Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_school

Retrieve a school's MaxPreps institutional record by ID, including address, enrollment, mascot, colors, and governing association to resolve the school behind a team after search.

Instructions

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
schoolIdYesSchool id from maxpreps-school-search or maxpreps-school-zip-search example(7bdc339f-7cbf-4728-b0c8-ed898929cf68)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It makes clear this is a single-record read that returns institutional data and that the id comes from prior search calls, but it says nothing about error behavior for an unknown schoolId, rate limits, or whether the response is nested/flat, leaving meaningful gaps.

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, front-loaded with identity ('school record by id') and followed by the return contents and the call ordering; every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read lookup with no output schema, the description covers input provenance, sequencing, and the full set of returned fields, which is everything an agent needs to call it correctly.

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% and the single parameter already documents its source (maxpreps-school-search or maxpreps-school-zip-search) with an example value. The description restates that provenance rather than adding format or validation detail, so it sits at the baseline.

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 names a specific verb and resource ('MaxPreps school record by id') and enumerates the returned fields (name, address, city, ZIP, state, colours, mascot, enrollment, school type, governing association), so an agent can distinguish it from the search/`school_zip_search` siblings that take different inputs.

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?

It gives explicit sequencing guidance: use it after maxpreps-school-search to resolve the school behind a team. It does not spell out exclusions (e.g., when to prefer school_proximal or nfhs_school instead), so it falls short of a full when/when-not/alternatives statement.

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

Deploy Server

Other Tools