Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nfhs_event

Fetch a single NFHS Network game or event by key to return its schedule, sport, level, scores, status, postseason flag, and participating teams and publishers.

Instructions

Get one NFHS Network event. Returns one game or event by key with its full schedule, sport, game type, gender, level, scores, status, postseason flag, participant teams and publisher identities. Broadcast ingest data, VOD keys, tickets and contact fields are not part of this contract. The site reads event detail from the echo service first and falls back to unity; this route mirrors that order. Use nfhs-events to discover the event key first.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does well: it lists the returned data contract, explicitly excludes broadcast ingest data, VOD keys, tickets, and contact fields, and discloses the echo-then-unity fallback order. It does not mention authentication, rate limits, or failure behavior, which keeps it from a 5.

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?

The description is front-loaded with the core operation and return contract, followed by useful exclusions and the discovery prerequisite. Every sentence contributes information needed to call and interpret the tool, with no obvious padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with no output schema and no annotations, the description is largely complete: it explains what is returned, what is excluded, and how to obtain the key. Minor gaps around error conditions and service prerequisites remain, but they are not central to normal invocation.

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?

The schema already documents the single key parameter fully, including its source and an example. The description reinforces that the key comes from nfhs-events but does not add format or validation details beyond the schema, so the baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Get one NFHS Network event,' and immediately scopes the result to a single game or event identified by key. It also distinguishes this tool from the discovery sibling by directing the agent to nfhs-events for the key.

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 gives a clear prerequisite and alternative path: use nfhs-events to discover the event key before calling this tool. It does not explicitly state when not to use the tool or describe error behavior for invalid keys, but the intended usage context is clear.

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