Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_school

Read-only

Get MaxPreps school record by id. Returns one school's institutional record by schoolId: name, address, city, ZIP, state, colours, mascot, enrollment, school type and the governing association (id, name, abbreviation, URL). Use it after maxpreps-school-search to resolve the school behind a team.

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": {
      "schoolId": "<schoolId>"
    },
    "name": "maxpreps_school"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolIdYesRequired school id from maxpreps-school-search or maxpreps-school-zip-search.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the returned record shape, but that largely duplicates the existing output schema and says nothing about behavior for invalid or stale schoolIds, caching, or rate limits. With annotations doing the heavy lifting, this is adequate but adds little behavioral context.

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 with zero filler; the core action leads and the workflow hint follows. Field enumeration is dense but scannable and relevant to a record lookup.

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 one-parameter read-only lookup with a full schema and an output schema, the definition covers purpose, the key source, and the workflow position. Minor gaps remain around failure modes for unknown IDs, but nothing essential to correct invocation is missing.

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 coverage is 100% and the single schoolId parameter is already documented in the schema as coming from school search. The description restates that the lookup is keyed by schoolId but adds no new syntax, format, or validity constraints, so the schema is doing the work.

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 ("Get MaxPreps school record by id") and enumerates the fields returned (name, address, city, ZIP, state, colours, mascot, enrollment, type, governing association). It also names the search tool it complements, so an agent can separate this lookup from the sibling search tools.

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 clear sequencing guidance: 'Use it after maxpreps-school-search to resolve the school behind a team,' which tells the agent this is a follow-up resolution step rather than a discovery tool. It stops short of explicit exclusions for the other siblings (contests, seasons, proximal) or mentioning the zip-search variant that the schema references.

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

All Crawlora MCP toolsInspect
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.

Resources