Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nfhs_event

Read-only

Get one NFHS Network game or event by key and return its full schedule, sport, game type, gender, level, scores, status, postseason flag, participant teams and publisher identities. Use nfhs_events to discover the event key first; an unknown key is a 404. The site reads event detail from the echo service first and falls back to unity, and this tool mirrors that order. Broadcast ingest data, VOD keys, tickets and contact fields are 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_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesEvent key from nfhs-events, for example gam00aa5c4cde.

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 declare readOnlyHint and openWorldHint, and the description adds real value beyond them: the internal echo-then-unity fallback order and the explicit exclusion list (broadcast ingest, VOD keys, tickets, contact fields). It does not discuss latency, caching, or rate limits, but the contract boundaries and 404 behavior are disclosed.

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?

Front-loaded with the verb and returned fields, then usage, then implementation and exclusion notes. Dense but each sentence carries information; the exclusion list is marginally over-detailed but still earns its place by bounding the contract.

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 no prose explanation, and the description still gives a useful field inventory. For a single-parameter read tool with annotations and an output schema, nothing an agent needs to invoke it correctly is missing.

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 single key parameter is already documented with an example. The description still adds meaning by tying the key to its source tool (nfhs_events) and defining what happens with an unknown key, which is more than the schema states.

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?

States a specific verb and resource ('Get one NFHS Network game or event by key') and enumerates the payload scope (schedule, sport, game type, gender, level, scores, status, postseason flag, participants, publishers). It is clearly distinguishable from the sibling nfhs_events, which it names as the discovery counterpart.

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?

Explicitly routes the agent: 'Use nfhs_events to discover the event key first; an unknown key is a 404.' It states the prerequisite and the failure mode, so the agent knows both when to call this tool and what input it needs before calling.

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