Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nfhs_suggest

Returns typeahead suggestions for schools and state associations from a partial name of at least 3 characters, with a schools-only scope option.

Instructions

Typeahead school and association suggestions. Returns typeahead suggestions for a partial name (at least 3 characters). The profiles scope (default) returns schools and state associations, matching the site's global search box; the schools scope returns schools only. Each item uses the school shape, so school items carry the full school identity and location fields. Use nfhs-schools for a paginated filtered search instead.

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": {
      "search_term": "<search_term>"
    },
    "name": "nfhs_suggest"
  }
}

Input Schema

Name	Required	Description
`size`	No	Number of suggestions, 1 to 500; defaults to 10
`scope`	No	Suggester scope: schools or profiles (default)
`search_term`	Yes	Partial name, at least 3 characters

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses key traits: minimum 3 characters, scope-dependent result composition, school-shaped items, and non-paginated typeahead behavior implied by directing pagination to nfhs-schools. It does not describe error handling for short terms or the full response envelope, but the main behavior is transparent.

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?

The description is front-loaded with the core purpose, then covers minimum length, scope behavior, item shape, and the alternative tool. It is appropriately sized and every sentence contributes useful guidance.

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?

Given no output schema and no annotations, the description provides enough context to invoke the tool correctly: partial-name constraint, scope semantics, result composition, and item shape. Minor gaps remain around exact response structure and error behavior for invalid input.

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. The description adds meaning beyond the schema by explaining what profiles versus schools scope returns and noting that school items use the full school shape, though it does not add much about the size parameter.

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 states a specific verb and resource: returns typeahead suggestions for partial school and association names. It distinguishes the two scopes and names the sibling tool nfhs-schools for paginated filtered search, so an agent can differentiate it from alternatives.

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 gives explicit usage conditions: partial name of at least 3 characters, profiles scope as default for global-search-style results, schools scope for schools only, and nfhs-schools for paginated filtered search. This clearly routes the agent between this typeahead tool and the alternative.

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

Deploy Server