Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nfhs_suggest

Read-only

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

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

NameRequiredDescriptionDefault
sizeNoOptional page size, 1 to 500; defaults to 10.
scopeNoOptional suggester scope: schools returns schools only, profiles also returns state associations. Defaults to profiles.
search_termYesFree-text term, at least 3 characters.

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.6/5.0
Behavior4/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 real context beyond them: the 3-character minimum, default scope behavior (profiles = schools + state associations, matching the global search box), and that every item follows the school shape so school items carry full identity and location fields. It does not discuss suggestion ranking or truncation behavior, which keeps it from a 5.

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 core purpose, then scope semantics, then the sibling routing. Minor overlap with the schema: the 'at least 3 characters' constraint and the schools-only scope are both restated from the parameter descriptions, but each restatement supports the routing narrative rather than padding.

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?

An output schema exists, so return values need not be explained, and annotations cover safety and openness. The description still states the input precondition, the scope default, and the item shape an agent should expect, leaving nothing material missing for a 3-parameter read-only suggester.

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 nevertheless earns credit by explaining what scope actually means in practice (default profiles includes state associations; schools-only excludes them) and by clarifying the semantic content of returned items, going beyond the terse schema wording.

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: 'Return typeahead school and state-association suggestions for a partial name of at least 3 characters.' It also names the sibling it is not (nfhs_schools) and the scope variant (scope=schools returns schools only), so an agent can distinguish it from the paginated search tool without opening any 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 states the positive case (typeahead over a partial name, mirroring the site's global search box) and gives an explicit alternative with its selecting condition: 'Use nfhs_schools when you need a filtered paginated search instead of typeahead.' That is a clear when-to-use / when-to-use-something-else pairing.

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