Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_json_constructors

Retrieve a Formula 1 season's constructors with each team's standings value, name, logo, and colour codes for use in team season results queries.

Instructions

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
seasonYesFour-digit championship year, 1950 through next season example(2026)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full transparency burden. It does disclose the return shape (value, name, logo, colour codes) and implies a read-only lookup keyed by season, but says nothing about pagination, failure behavior for out-of-range seasons, or that results are narrowly scoped to a single season's dropdown.

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?

Two sentences, front-loaded with the resource and result contents, with the downstream-consumer note last. No filler, though the 'discovery surface' phrasing is slightly indirect compared to simply naming the tool it feeds.

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?

There is no output schema, so the description's field list (value, name, logo, colour codes) is doing necessary work and is sufficient for a simple one-parameter lookup. Behavioural edge cases remain unstated, but the core call path is covered.

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 coverage is 100% and the single parameter already documents 'Four-digit championship year, 1950 through next season'. The description only reinforces that this returns one season's list, adding essentially no syntax or constraint detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (Formula 1 constructors) and states exactly what comes back: each team's value, name, logo and colour codes. The closing sentence ties it to formula1-team-season-results, which separates it from the standings/team tools. It stops short of distinguishing it from similarly named siblings like formula1_team_grid or formula1_json_team_assembly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'discovery surface for the team value formula1-team-season-results accepts' tells an agent to call this before that tool, but there is no explicit when-to-use/when-not-to-use framing and no named alternative for the opposite case.

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