College Scorecard

Get School

get_school

Read-onlyIdempotent

Get detailed info for a specific college by its College Scorecard ID. Returns tuition, admission rate, student size, median earnings after 10 years, completion rate, and median debt.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	College Scorecard school ID (numeric, from search results)
`_apiKey`	Yes	api.data.gov API key

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	College Scorecard ID
`url`	No	School website URL
`zip`	No	ZIP code
`city`	No	City location
`name`	No	School name
`state`	No	State code
`ownership`	No	Public, Private nonprofit, or Private for-profit
`median_debt`	No	Median debt for completers
`student_size`	No	Total enrolled students
`admission_rate`	No	Admission rate (0-1)
`completion_rate`	No	Completion rate (0-1)
`tuition_in_state`	No	In-state tuition cost
`median_earnings_10yr`	No	Median earnings 10 years after entry
`tuition_out_of_state`	No	Out-of-state tuition cost

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-college-scorecard-api-key",
-    "id": 110662
-  }
-]New value: +[
+  {
+    "id": 110662
+  }
+]

First observedJun 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool is clearly safe and non-mutating. The description adds value by specifying the exact data fields returned (tuition, admission rate, etc.), which gives behavioral context beyond annotations. No contradictions.

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?

The description is a single concise sentence that provides the core purpose and lists key data points. It is front-loaded with the main action (Get detailed info) and resource. Slightly more detail on return format could be useful, but it is efficient.

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?

Given the tool's simplicity (2 parameters, both required, full schema coverage) and an output schema (which likely documents return structure), the description is sufficient. It lists the key data fields returned, which covers what an agent needs to know. The only minor gap is not explicitly stating that the ID comes from search results, but that is in the parameter description.

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

Parameters3/5

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

Schema description coverage is 100%, meaning both parameters (id and _apiKey) are fully described in the schema. The description adds context that id is a College Scorecard ID, but this is already in the schema. The description does not add substantial meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the tool fetches detailed information for a specific college using its College Scorecard ID, listing specific data fields returned. It distinguishes itself from siblings like search_schools (which likely searches/filters) by focusing on a single college retrieval.

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?

The description implies that this tool is for fetching details for a specific college ID, which likely comes from search results, as indicated in the parameter description. However, it does not explicitly state when to use this tool instead of search_schools or other tools, nor does it mention alternatives for similar tasks.

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

All College Scorecard 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.