Skip to main content
Glama

My admission odds

my_odds
Read-onlyIdempotent

Estimate a student's admission odds at one or more colleges, by round, with a likely range, from GPA and test scores (plus optional class rank, home state, legacy, first-generation, aid). Same model as prefrosh.ai/chance. Always tell the user this is an estimate from grades and scores only; essays, activities and recommendations can move it a lot. Needs at least a GPA or a test score; ask for them if missing rather than guessing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "schools": "<schools>"
    },
    "name": "my_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
actNoBest ACT composite.
gpaNoUnweighted GPA, ideally on a 4.0 scale (a 100-point average also works).
satNoBest total SAT (superscore is fine).
legacyNoA parent attended this college.
schoolsYesCollege names.
first_genNoFirst in family to attend a four-year college.
needs_aidNoWill apply for need-based aid (default true).
class_rankNoClass rank bucket, if known (percent of class).
home_stateNoTwo-letter US state the student lives in (matters for public universities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so safety is covered; the description adds genuinely new behavioral context by warning that the estimate ignores essays, activities and recommendations and by referencing the underlying model. It does not cover failure modes (e.g. unrecognized college names) or output detail, so not 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.

Conciseness5/5

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

Purpose first, then credibility, then the two agent-facing obligations, all in three tight sentences with no filler. Every clause (inputs, caveat, missing-data rule) changes how the agent calls or reports the tool.

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?

With no output schema, saying the result is a 'likely range' by round usefully previews the return shape, and the input requirements are fully covered. The one loose end is the 'by round' phrasing, which implies an admission-round dimension that no parameter exposes, leaving the agent unsure whether round is fixed or assumed.

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, but the description adds a cross-parameter rule the schema cannot express: only 'schools' is required, yet at least one of GPA or a test score must be supplied, and the agent should ask rather than invent one. It also groups the optional factors, matching the described inputs to the parameter set.

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?

States a specific verb and resource ('Estimate a student's admission odds at one or more colleges') plus the inputs it derives from and the shape of the answer ('with a likely range'). That framing is clearly a read-only calculation, which implicitly separates it from the game_* / game_vote siblings without needing to name them.

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?

Gives concrete preconditions ('Needs at least a GPA or a test score; ask for them if missing rather than guessing') and an instruction to always caveat the result to the user. It does not name an alternative sibling or state when not to use it, so it stops short of the top band.

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