Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nfhs_producer

Look up one NFHS Network producer by key to retrieve identity, type, state-association linkage, coverage, colors, social links, and related publishers referenced in school and event records.

Instructions

Get one NFHS Network producer. Returns one producer record by key: identity, type, state-association linkage, state coverage, colours, social links and related publishers. Producer keys appear in school and event records. Use nfhs-publisher for the publisher that fronts a producer. Device and contact data is 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_producer"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesProducer key, for example pdc1e100ffe6e

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden — and it does meaningful work by enumerating the returned record contents (identity, type, state-association linkage, coverage, colours, social links, related publishers) and explicitly excluding device and contact data from the contract. It stops short of stating read-only safety, error behavior on an invalid key, or auth requirements, which matters when no annotations back it up.

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?

Four short sentences, front-loaded with what the tool does and its return shape, followed by key provenance and the sibling routing note. Every sentence earns its place — the field enumeration and the exclusion both change how the agent interprets the result.

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 single-parameter, no-output-schema read tool, the description covers everything needed: what it returns, how to get the key, what is deliberately not included, and which sibling handles the adjacent concept. Nothing essential to a correct call is left to inference.

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% and the schema already supplies an example key format, so the baseline would be a 3. The description adds genuine meaning beyond the schema by explaining that producer keys are surfaced inside school and event records, which tells the agent how to obtain a value for the required 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?

Opens with a specific verb and resource ("Get one NFHS Network producer") and immediately scopes it as a single-record key lookup. It then explicitly separates itself from the nearest sibling: "Use nfhs-publisher for the publisher that fronts a producer." An agent can distinguish this from nfhs_publisher and nfhs_schools 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 Guidelines4/5

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

The description names the concrete alternative (nfhs-publisher) and states the condition that selects it, and it tells the agent where producer keys come from ("Producer keys appear in school and event records"). What's missing is a negative condition such as what to do when the key is unknown, but the routing guidance is clear and actionable.

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