Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nfhs_publisher

Read-only

Get one NFHS Network publisher by key and return its identity, type, state-association linkage, state coverage, colours, social links, network/subscription flags and related producers. Publisher keys appear in an event's publishers list and in school records; use nfhs_producer for the producer behind a publisher. 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_publisher"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesPublisher key from an event's publishers list or a school record, for example cdb81ad6cb.

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.4/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 meaningful behavior beyond them: an unknown key yields a 404, and device/contact data is deliberately excluded from the contract, which sets an expectation about missing fields. It does not discuss pagination or rate behavior, but a single-key lookup needs neither.

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, all front-loaded with the core action first, then key provenance/routing, then error and data-boundary caveats. The returned-field enumeration is long and partly duplicative of the output schema, but it aids selection rather than wasting space.

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 the return payload need not be explained further; the description covers the remaining gaps an agent needs — where keys come from, the 404 behavior on bad input, the deliberate exclusion of contact/device data, and the sibling relationship. Nothing material is missing for a one-parameter read.

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 description coverage is 100% and the single key parameter already documents its provenance ('from an event's publishers list or a school record') along with a format example. The description's statement about where keys appear largely repeats that, so it adds little new meaning beyond the schema baseline.

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?

Specific verb (Get) plus a single, count-limited resource (one NFHS Network publisher by key), followed by a concrete enumeration of what is returned: identity, type, state-association linkage, state coverage, colours, social links, flags, related producers. It also explicitly separates this tool from nfhs_producer, so an agent can choose between the two on the description alone.

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?

Names the exact precondition for obtaining a key ('appear in an event's publishers list and in school records') and explicitly routes the agent to nfhs_producer for the producer behind a publisher. That is a when-to-use plus a named alternative with the distinguishing condition.

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