Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_json_constructors

Read-only

Get Formula 1 constructors from the JSON API. Returns one season's constructor dropdown: each team's value (the standings identifier), name, logo image and team colour codes. This is the discovery surface for the team value formula1-team-season-results accepts.

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": {
      "season": "<season>"
    },
    "name": "formula1_json_constructors"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonYesRequired four-digit championship year; the JSON dropdowns serve 1950 through next season.

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
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-source profile is covered. The description adds that the result is a single season's dropdown and enumerates the fields it carries (identifier value, name, logo, colours), which helps an agent know what it can reuse downstream. It says nothing about upstream API latency, rate limits, or failure modes, so with annotations carrying the safety burden a 3 is appropriate.

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?

Three short sentences, front-loaded with the verb and resource, then the returned payload, then the downstream purpose. Every sentence carries routing or payload information; nothing is padding.

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?

A one-parameter read tool with a full output schema and clear annotations; the description supplies the one thing structured fields cannot — that this is the lookup step feeding the team-results tool. Nothing an agent needs in order to call it correctly is missing.

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 schema already documents `season` as a required four-digit year spanning 1950 through next season. The description adds no syntax, format, or edge-case guidance beyond that, so the baseline 3 applies — the structured field does the work.

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 Formula 1 constructors") plus the exact shape of the payload: per-team value/standings identifier, name, logo image, and colour codes. It also positions itself against the team-results tool by calling itself "the discovery surface for the team value formula1-team-season-results accepts," so an agent can distinguish it from formula1_team and formula1_team_grid without opening a 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?

Gives a clear usage context: call this to obtain the team value the season-results tool consumes, which implies a resolve-then-query workflow. It stops short of explicit exclusions (e.g., when to prefer formula1_team_grid or formula1_team instead for roster/identity data), leaving some sibling routing to inference.

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