Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nascar_series

Read-only

Discover the native NASCAR source series groups in one published annual feed and return every series id with its source group key. These are native group identifiers, not invented current sponsor labels; use nascar_season_races to read the race ids inside a group. season is optional and defaults to the current UTC calendar year, and the endpoint does not collect other seasons or invent a closed season list. The annual metadata read is cached five minutes per process.

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": "nascar_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional published native calendar year, for example 2025. Omit it for the current UTC calendar year.

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.1/5.0
Behavior4/5

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

Annotations already cover the read-only, open-world profile, and the description adds genuinely new behavior: a five-minute per-process metadata cache, which lets an agent reason about staleness. It also warns that responses are native group keys rather than current sponsor labels, preventing a naming misinterpretation. It stops short of describing rate limits or failure modes.

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, front-loaded with the core action, then the sibling pointer, then the parameter/caching notes. It is dense but earns most of its space; the 'not invented current sponsor labels' aside is a slightly awkward defensive phrasing.

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?

An output schema exists, so return values needn't be spelled out, yet the description still summarizes them. Combined with the cache note and season default, an agent has enough to call this correctly; only explicit error/empty-result behavior is absent.

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?

With a single parameter at 100% schema coverage, the schema already documents the default behavior. The description reinforces 'optional, defaults to the current UTC calendar year' and adds the useful nuance that no closed season list is published, but it adds little beyond the schema text.

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 concrete verb+resource ('Discover the native NASCAR source series groups in one published annual feed') and states the return shape ('every series id with its source group key'). It explicitly separates itself from nascar_season_races, so an agent can route correctly without opening either 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 names the alternative sibling and what that sibling is for ('use nascar_season_races to read the race ids inside a group'), plus a clear boundary that other seasons are not collected. There is no explicit 'do not use this when...' clause for other cases, but the routing context is strong.

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