Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_team_grid

Retrieve the current Formula 1 team grid with team names, colours, profile links, and named drivers; the payload reports the season shown on the page header.

Instructions

The Formula 1 team grid the site currently shows. Returns the current team grid: each team's name, team colour, profile slug, profile URL and the drivers the card names. The team page has no season selector (a season query is ignored upstream), so the route describes the season the page header names and reports that season in the payload.

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_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a genuine behavioral trap: a season query is ignored upstream because the team page has no season selector, and the payload instead reports the season the page header names. That is non-obvious and prevents a wrong assumption, though freshness/caching and whether the list is paginated or fixed-size are not addressed.

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?

The key fact – current team grid with these fields – is front-loaded, and the season caveat follows. The opening two clauses ('The Formula 1 team grid the site currently shows. Returns the current team grid:') restate the same idea and could be merged.

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 zero-parameter read tool with no output schema, the description supplies everything needed: the record fields returned, the season semantics, and the absence of a season selector. Nothing required 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4. The description additionally clarifies that no season can be targeted and that any season input would be silently dropped, which is useful framing even though the schema exposes no such property.

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 and scope ('the current team grid') and enumerates what each entry contains (name, colour, slug, URL, drivers). It implicitly contrasts with formula1_driver_grid by saying 'team grid', but never names a sibling explicitly, so differentiation is left to the reader.

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 only implied by 'the site currently shows' and 'the team page has no season selector' – an agent can infer this is the current-season snapshot. There is no explicit when-to-use versus when-to-call formula1_team_standings or formula1_team_season_results, and no stated alternatives.

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