college-scorecard-mcp-server

Get School Profile

scorecard_get_school

Read-onlyIdempotent

Institutional profiles for one or more school IDs. Accepts up to 1,000 elements, deduplicates normalized IDs, serves the first 100 distinct IDs, and reports missing and unprocessed IDs separately. Use scorecard_compare_schools for comparisons. Custom fields return requested paths and their JSON values in selected_fields, absent paths in absent_fields, and real identity; default profiles include costs, admissions, outcomes, aid, and completion rates.

Input Schema

Name	Required	Description
`id`	Yes	Positive safe integer school ID or up to 1,000 raw elements. First 100 distinct normalized IDs served; discover IDs with scorecard_search_schools.
`fields`	No	Optional comma-separated list of custom field paths from scorecard_list_fields. Overrides the default field set.
`program_limit`	No	Projected program positions per parent array; values above 100 are clamped to 100.
`program_offset`	No	Zero-based position in each projected program parent array.

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Warning when some requested IDs returned no record.
`schools`	No	Full profiles for the requested school(s).
`truncated`	No	True when any projected program parent has remaining positions.
`missing_ids`	No	Processed distinct IDs with no returned record.
`total_found`	No	Number of records returned.
`total_requested`	No	Number of IDs requested.
`unprocessed_ids`	No	Distinct IDs beyond the 100-ID serving cap, in caller order.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedNov 3, 2026

addedInput schema / properties / program_limit

Added value: +{
+  "default": 20,
+  "description": "Projected program positions per parent array; values above 100 are clamped to 100.",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / program_offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based position in each projected program parent array.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / schools / items / properties / attendance_basis

Added value: +{
+  "description": "Period of the effective attendance cost, selected independently of tuition.",
+  "enum": [
+    "academic_year",
+    "program_year"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / schools / items / properties / attendance_program_year

Added value: +{
+  "description": "Reported program-year cost of attendance.",
+  "type": "number"
+}

changedOutput schema / properties / schools / items / properties / cost_of_attendance / description

Previous value: -"Total cost of attendance per year."New value: +"Available academic-year attendance cost, otherwise program-year cost."

addedOutput schema / properties / schools / items / properties / effective_tuition

Added value: +{
+  "description": "Available academic-year tuition, otherwise program-year tuition.",
+  "type": "number"
+}

addedOutput schema / properties / schools / items / properties / metric_scope

Added value: +{
+  "additionalProperties": false,
+  "description": "Earnings, debt and repayment are pooled at OPEID6; completion is campus-specific.",
+  "properties": {
+    "completion": {
+      "const": "campus",
+      "description": "Completion is campus-specific.",
+      "type": "string"
+    },
+    "debt": {
+      "const": "opeid6",
+      "description": "Debt is OPEID6-pooled.",
+      "type": "string"
+    },
+    "earnings": {
+      "const": "opeid6",
+      "description": "Earnings are OPEID6-pooled.",
+      "type": "string"
+    },
+    "repayment": {
+      "const": "opeid6",
+      "description": "Repayment is OPEID6-pooled.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "earnings",
+    "debt",
+    "repayment",
+    "completion"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / schools / items / properties / ope6_id

Added value: +{
+  "description": "Provider OPEID6 identifier, preserving leading zeros.",
+  "type": "string"
+}

addedOutput schema / properties / schools / items / properties / program_pages

Added value: +{
+  "description": "Per-parent program array paging in provider order; continuation applies to this school.",
+  "items": {
+    "additionalProperties": false,
+    "description": "One projected program parent page.",
+    "properties": {
+      "continuation": {
+        "additionalProperties": false,
+        "description": "Selectors to request for this school next.",
+        "properties": {
+          "program_limit": {
+            "description": "Effective page limit.",
+            "type": "number"
+          },
+          "program_offset": {
+            "description": "Next requested position.",
+            "type": "number"
+          }
+        },
+        "required": [
+          "program_offset",
+          "program_limit"
+        ],
+        "type": "object"
+      },
+      "nextOffset": {
+        "description": "Next position when more remain.",
+        "type": "number"
+      },
+      "offset": {
+        "description": "Zero-based requested position.",
+        "type": "number"
+      },
+      "parent_path": {
+        "description": "Provider program parent path.",
+        "type": "string"
+      },
+      "shown": {
+        "description": "Positions returned.",
+        "type": "number"
+      },
+      "total": {
+        "description": "Total provider positions before paging.",
+        "type": "number"
+      },
+      "truncated": {
+        "description": "Whether positions remain after this page.",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "parent_path",
+      "total",
+      "offset",
+      "shown",
+      "truncated"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / schools / items / properties / tuition_basis

Added value: +{
+  "description": "Period of the effective tuition.",
+  "enum": [
+    "academic_year",
+    "program_year"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / schools / items / properties / tuition_program_year

Added value: +{
+  "description": "Reported program-year tuition and fees.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when any projected program parent has remaining positions.",
+  "type": "boolean"
+}

First observedOct 13, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered; the description adds the genuinely important batch semantics — 1,000 accepted, deduplication of normalized IDs, only the first 100 distinct IDs served, and missing versus unprocessed reported separately. The phrase 'real identity' is unexplained jargon, keeping this short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the resource and the batch limits, then the sibling alternative, then field semantics — a logical ordering with no wasted clauses. It is dense and a few phrases ('real identity') are opaque rather than concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, read-only lookup with a full schema and an output schema, the description supplies the batching, truncation, and field-override behavior an agent needs to call it correctly. Remaining gaps (pagination of program arrays, return shape) are covered by the structured fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining what the fields parameter produces (requested paths and their JSON values in selected_fields, absent paths in absent_fields) and by enumerating the default field set. It does not cover program_limit clamping, but that is documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific resource and scope ('Institutional profiles for one or more school IDs') and immediately distinguishes itself from the sibling compare tool. An agent can tell what it returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes comparisons to scorecard_compare_schools and explains that custom fields require scorecard_list_fields while omitting the argument yields the default profile. It does not restate the schema's guidance about discovering IDs via scorecard_search_schools, but the when-to-use context is otherwise clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All college-scorecard-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.