Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nfhs_school

Retrieve a single NFHS Network school profile by key or slug, including identity, mascot, address, colors, logo, and network/subscription flags.

Instructions

Get one NFHS Network school. Returns one school by its key or slug with identity, mascot, acronym, address, city, state, coordinates, colours, logo, network/subscription flags, publisher and producer keys and share image. Contact fields, subscriber emails and Pixellot device mappings are not part of this contract. Use nfhs-schools or nfhs-suggest to discover the key or slug first.

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, for example 0004954463 or covington-high-school-covington-tx

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does substantial work: it enumerates the returned payload and explicitly excludes contact fields, subscriber emails and Pixellot device mappings, defining a contract boundary an agent could not otherwise infer. It stops short of stating read-only semantics explicitly, missing-key behavior, or auth requirements.

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?

Three sentences, front-loaded with the operation and followed by returns, exclusions, and the discovery prerequisite in a logical order. The long run-on field enumeration in sentence two is dense but justified given there is no output schema.

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 single-parameter read tool with no output schema, the description compensates by describing the return payload and its exclusions, and it routes the agent to discovery siblings for the identifier. Only the not-found/error path and any permission or rate constraints remain unstated.

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 parameter already documents "School key or slug" with two concrete examples. The description's "by its key or slug" restates the schema rather than adding format, uniqueness, or case-sensitivity guidance, so 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?

"Get one NFHS Network school" states a specific verb and resource with explicit cardinality (one), which cleanly separates it from the plural lister nfhs_schools and the lookup helper nfhs_suggest. An agent can identify the operation 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 Guidelines4/5

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

It gives an explicit prerequisite: obtain the key or slug via nfhs_schools or nfhs_suggest before calling. What's absent is the inverse rule — e.g., that enumerating many schools should use nfhs_schools rather than repeated single calls — but the discovery pointer covers the main misuse path.

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