Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nfhs_school

Read-only

Get one NFHS Network school by key or slug and return its identity, mascot, acronym, address, city, state, coordinates, colours, logo, network/subscription flags and publisher/producer identities. Use nfhs_schools or nfhs_suggest to discover the key or slug first; an unknown key is a 404. Contact fields, subscriber emails and Pixellot device mappings are deliberately not part of this contract.

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": {
      "key": "<key>"
    },
    "name": "nfhs_school"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesSchool key or slug from nfhs-schools or nfhs-suggest, for example 0004954463 or covington-high-school-covington-tx.

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real value with the 404-on-unknown-key behavior and an explicit negative scope (contact fields, subscriber emails, Pixellot device mappings are not returned). That negative scope usefully prevents an agent from fishing for absent fields, though nothing is said about rate limits or response size.

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?

Two sentences, front-loaded with the action and its scope, then the discovery/error guidance. The long field enumeration is dense but earns its place by signalling what is and isn't returned; a slightly tighter phrasing would avoid reading like a data dictionary.

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?

With an output schema present and a fully documented single parameter, the description only needs to cover intent, prerequisite, and failure mode — all of which it does, plus deliberate omission notes. Nothing an agent needs in order to call this correctly 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 schema already documents the single key parameter with both example formats, so the description's "by key or slug" is largely redundant. What it does add is provenance for the value (obtainable from nfhs_schools/nfhs_suggest) and error semantics, which is baseline-plus rather than substantive parameter elaboration.

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 opens with a specific verb and resource ("Get one NFHS Network school by key or slug") and then enumerates the returned facets, which clearly separates it from the sibling list/discovery tools nfhs_schools and nfhs_suggest. An agent can identify the single-record lookup contract without opening the schema.

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

Usage Guidelines5/5

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

It explicitly states the prerequisite workflow ("Use nfhs_schools or nfhs_suggest to discover the key or slug first") and the failure condition ("an unknown key is a 404"). Both the when-to-use path and the negative outcome are given, leaving nothing to inference.

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