Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nfhs_producer

Read-only

Get one NFHS Network producer by key and return its 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. An unknown key is a 404, and device/contact data is 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_producer"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesProducer key from a school or event record, for example pdc1e100ffe6e.

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

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

With readOnlyHint and openWorldHint already declared, the description still adds real behavioral content: an unknown key yields a 404, and device/contact data is deliberately excluded from the contract. These are failure-mode and scope facts the annotations cannot express, 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?

Three sentences, front-loaded with the action and return surface, then sibling routing, then failure/scope notes. The field enumeration in sentence one is slightly listy and partly redundant with the output schema, but it still aids tool selection 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?

For a single-parameter read with a full output schema and annotations, the description covers the remaining gaps an agent needs: where the key originates, the 404 failure mode, the sibling alternative, and an explicit exclusion of device/contact data. Nothing material is left to guesswork.

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's own description already states that the key comes from a school or event record and gives the example format 'pdc1e100ffe6e'. The prose repeats that provenance without adding format rules, validation behavior, or casing constraints, so this is baseline territory.

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 by key") and enumerates the returned facets (identity, type, state-association linkage, coverage, colours, social links, publishers). It explicitly separates itself from the nearest sibling, nfhs_publisher, so an agent can choose between them without opening a 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?

Gives concrete routing context: producer keys come from school and event records, and nfhs_publisher is named for the adjacent case of the publisher fronting a producer. What's missing is an explicit statement of when a producer lookup is the wrong call beyond that one sibling comparison (e.g., whether a batch or search path exists).

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