Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nfhs_association

Read-only

Get one NFHS Network state association or section by key or slug and return its about text, colours, social links, state coverage and publisher, producer and championship-page identities. Use nfhs_associations to discover the key or slug first; an unknown key is a 404 and a valid empty field stays null rather than being invented.

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_association"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesAssociation key or slug from nfhs-associations, for example ghsa or 18bad24aaa.

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?

Beyond the readOnlyHint/openWorldHint annotations, it discloses concrete behavior: an unknown key yields a 404, and valid empty fields remain null rather than being fabricated, which tells the agent not to treat nulls as errors. It does not mention rate limits, caching, or payload size, but the safety and error semantics are well covered.

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?

Two sentences, front-loaded with the action and resource, followed by the prerequisite and error semantics; nothing is padding. The middle clause enumerating returned fields is somewhat dense but earns its place by signalling the shape of the response.

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 tool with an output schema and read-only annotations, the description covers the remaining gaps: how to obtain the key, what happens on an unknown key, and how nulls should be interpreted. An agent has enough to invoke it correctly and interpret failures.

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 parameter already documents 'association key or slug' with examples ghsa and 18bad24aaa, so the description's mention of 'key or slug' adds little. The routing hint about obtaining the key from nfhs_associations is useful context but is usage guidance rather than added parameter meaning.

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 names a specific verb and resource ('Get one NFHS Network state association or section') and specifies the lookup key ('by key or slug'), which cleanly separates it from the plural sibling nfhs_associations that lists them. An agent can identify the single-entity retrieval tool without opening the 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?

It gives clear routing guidance by naming nfhs_associations as the discovery step before calling this tool, which is a real workflow prerequisite. It does not explicitly state exclusions (e.g., when to fetch a section versus an association, or when to jump straight to publisher/producer tools), so it stops short of full when/when-not coverage.

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