Skip to main content
Glama

Out-of-state tuition penalty ranking

out_of_state_penalty

Find out how much 30-year net present value a non-resident loses compared to a resident at U.S. public four-year colleges, with tuition figures included.

Instructions

U.S. public four-year colleges ranked by the out-of-state penalty: how much 30-year NPV a non-resident gives up versus a resident at the same school. Includes both NPVs and both tuition figures per row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows returned (77 total).
stateNoFilter to one state's public colleges.
Behavior3/5

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

No annotations are provided, so description must carry full burden. It states the tool returns rankings with specific data per row (NPVs, tuition) but does not disclose read-only nature, data source, update frequency, or any side effects. Adequate but missing some transparency.

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

Conciseness5/5

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

Two sentences: first covers purpose, second covers output content. No wasted words, appropriately sized.

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?

No output schema, but description explains return values (NPVs, tuition figures per row). However, it does not specify ordering direction (e.g., descending penalty) or the default sort. Mostly complete.

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 parameter definitions are already complete. Description does not add meaning beyond schema; it only mentions what is included per row (output), not parameters. Baseline 3 applies.

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 it ranks U.S. public four-year colleges by out-of-state penalty, defines the penalty as NPV difference, and mentions included data (NPVs, tuition). This distinguishes it from siblings like best_value_colleges and search_colleges.

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

Usage Guidelines3/5

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

The description implies use when interested in out-of-state penalty ranking but does not explicitly state when to use this tool versus alternatives like best_value_colleges or search_colleges. No exclusions or when-not-to-use guidance provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thomasthinks/college-roi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server