Skip to main content
Glama

BRAINIAC Public Infrastructure Lookups

US College Scorecard lookup

public-infrastructure_college-scorecard-lookup
Read-onlyIdempotent

Look up cost, admission, completion, earnings and debt fields from the College Scorecard. Price $0.02 USDC. POST /api/v1/public-infrastructure/college-scorecard-lookup. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "public-infrastructure_college-scorecard-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoname, string, length 3 to 200. Optional.
limitNolimit, integer, from 1 to 25. Required.
opeIdNoopeId, string, length 1 to 20. Optional.
stateNostate, string, length 2 to 2. Optional.
unitIdNounitId, string, length 1 to 20. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
dataUpdatedNodataUpdated. String.
limitationsNolimitations. Array.
institutionsNoinstitutions. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 genuinely useful context beyond that: the $0.02 USDC price, the POST endpoint, and the x402 paywall behavior where unpaid calls return payment terms without executing. This is exactly the kind of operational detail annotations cannot express.

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?

Three sentences, front-loaded with the data categories before pricing and endpoint details. The raw path/route text is mild boilerplate, but nothing is padded or wasted.

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?

An output schema exists, so return values need not be explained. The description covers purpose, cost, endpoint, and paywall behavior; the only missing piece is filter-combination guidance for a five-parameter tool, which keeps it from a 5.

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%, so the schema already documents all five parameters including lengths and the default limit of 25. The description adds no filter semantics beyond the schema, making the baseline 3 correct.

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

Purpose4/5

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

The description names a specific verb (look up) and a clearly scoped resource (College Scorecard) and enumerates the data categories returned: cost, admission, completion, earnings, debt. This distinguishes it from sibling public-infrastructure lookups by domain, though it does not explicitly name those siblings.

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

Usage Guidelines2/5

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

The description never says when to use this tool versus alternatives, nor how the optional filters (name, state, opeId, unitId) should be combined or which to prefer. It provides no usage conditions beyond the payment mechanics.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources