Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nfhs_activities

Lists NFHS Network sports and non-sport activities to find exact names that event and highlight filters accept; filter results by sport or top-sport flags.

Instructions

List NFHS Network activities and sports. Returns the complete activity list NFHS Network serves: sports plus non-sport activities such as graduation, band performance and assembly, with each record's sport, two-team, indoor, championship and top-sport flags. Use this discovery endpoint to obtain the exact activity names the nfhs-events and nfhs-highlights activity filter accepts, matched case-insensitively. The upstream list is complete and ordered; is_sport and is_top_sport are filtered locally against the upstream's own flags.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nfhs_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_sportNoOptional sport flag filter; true returns only sports
is_top_sportNoOptional top-sport flag filter; true returns the 12 promoted top sports

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does disclose meaningful behavior: the upstream list is complete and ordered, matching is case-insensitive downstream, and is_sport/is_top_sport filtering happens locally against the upstream's own flags rather than server-side. It omits operational context such as auth, rate limits, or failure modes, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all load-bearing: what it returns, why to call it, and how filtering actually behaves. Slightly dense mid-sentence record-field enumeration, but nothing is redundant and the core purpose is front-loaded.

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?

No output schema exists, and the description compensates by naming the per-record fields (sport, two-team, indoor, championship, top-sport flags) and asserting the list's completeness and ordering. For a two-optional-parameter discovery tool, an agent has everything needed to call it and interpret the result correctly.

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%, so a 3 is the baseline; the description earns above that by revealing the non-obvious implementation detail that both filters are applied locally against the upstream's own flags. It does not add anything about the 12-item top-sport set beyond what the schema already 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 (list) and resource (NFHS Network activities and sports) and immediately clarifies scope: sports plus non-sport activities such as graduation, band performance and assembly. It also enumerates the per-record attributes returned, so an agent knows this is a discovery/enumeration endpoint rather than a search or detail lookup.

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?

Explicitly frames it as a discovery endpoint whose purpose is to obtain the exact activity names accepted by the nfhs-events and nfhs-highlights activity filter, which tells the agent when to prefer it. It stops short of stating when not to use it (e.g., when activity names are already known) or contrasting it with the nfhs_sports sibling.

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