At least for shuttle, the MCC had a lot more detailed information than the crew does.
The crew was only provided with the information necessary for situational awareness and procedure execution. The MCC got a lot of detailed engineering data that the crew would not normally need. If they did end up needing it, they could get it from the MCC.
Here are some examples for a single system, the Remote Manipulator System (the robot arm).
The crew had a control panel that provided them with status indicator and caution lights, a rate meter, and three digital displays that could display one of 7 sets of data at a time.
(Personal photograph from shuttle Endeavour)
They also had two computer displays. One provided status information, much of which was duplicated on the hardware panel. The second provided more detailed information on malfunctions.
(Source: DPS Dictionary)
The Payload Deployment and Retrieval System flight controllers had access to much more information. Some of their displays are shown in this picture.
They also had generic capabilities like plotting graphs of any desired telemetry parameter.
A simple example of the difference between what the crew saw and the flight controller saw is as follows:
Let's say the crew encountered a malfunction of the arm's end effector while grappling a payload. The crew would get a caution light and tone, a fault message on the CRT screen, and possibly one or more "down arrows" under the CHECK CRT heading on the malfunction computer screen. The control panel also had six "talkbacks" giving information on the status microswitches in the end effector.
The flight controller would see the parameters that drove all these crew displays, and much more:
- Plots of the current being drawn by the motors in the end effector mechanism.
- Detailed telemetry information about the end effector drive commands generated by the Manipulator Control Interface Unit (MCIU) firmware in response to crew commands.
- Event time logs showing precisely when crew commands were entered in relation to when error messages or relevant telemetry data were emitted
- Telemetry showing whether relevant switch contacts are "made" or "broken" corresponding to the physical switch position
- Status of other internal flags generated by the MCIU according to its interpretation of the grapple's progress
- Built-In Test Equipment (BITE) status generated by the system
The flight controllers also had access to reference information not available to the crew: software listings, detailed schematics, engineering support from the Mission Evaluation Room, etc.