Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_team_standings

Retrieve a Formula 1 season's constructors' championship table with team positions, points, and standings URL, so you can check team rankings for any year from 1958 onward.

Instructions

Formula 1 constructors' championship standings. Returns one season's constructors' championship table: position, team, points and the team standings URL. The constructors' championship started in 1958; a pre-1958 season returns available=false with an empty table, and a season the site has not published yet returns an empty table.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoFour-digit championship year, 1950 through the current season; defaults to the current season example(2026)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses the response shape (position, team, points, standings URL) and two distinct edge behaviors — a pre-1958 season returns available=false with an empty table, and an unpublished season returns an empty table. It does not mention error responses or whether the data is scraped/live-updated, but for a public read-only statistics lookup the disclosure is solid.

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 sentences, front-loaded with what is returned, followed by the historical cutoff and the two empty-table cases. No filler, no repetition of the tool name, and every clause conveys operational information.

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?

For a single-optional-parameter read tool with no annotations and no output schema, the description supplies the return fields, the valid season semantics, and the degenerate cases. There is nothing else an agent would need in order 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 the baseline is 3, but the description adds genuine domain meaning beyond the schema: the schema merely says '1950 through the current season', while the description explains that constructors' data only exists from 1958 and what happens for earlier years. That materially changes how an agent should read the parameter's valid range.

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 — "Returns one season's constructors' championship table" — and enumerates the returned fields (position, team, points, standings URL). The 'constructors'' qualifier cleanly separates it from the sibling formula1_driver_standings without needing the schema.

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 by the output description rather than stated as guidance; there is no explicit 'use this when you want team rather than driver standings' routing, and no named alternative. It does, however, give useful boundary conditions for out-of-range seasons (pre-1958 → available=false, unpublished season → empty table), which helps an agent interpret results.

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