Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_team_standings

Read-only

Get one Formula 1 season's constructors' championship table and return position, team, points and the team profile slug. Use season in four-digit form; the constructors' championship started in 1958, so a pre-1958 season returns an explicitly unavailable empty table rather than a fabricated one. Use the team slug with formula1_team.

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
seasonNoOptional four-digit championship year; the constructors' championship started in 1958, and a pre-1958 season returns an empty table. Defaults to the current 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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a pre-1958 season yields a deliberate 'unavailable' empty table rather than fabricated data, which tells the agent how to interpret degenerate results. Return shape detail is partially redundant with the output schema but harmless.

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 purpose, then the historical constraint, then the follow-up tool. Nothing is filler and the ordering follows how an agent would actually reason about the call.

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 one-optional-parameter read tool with a full output schema and readOnly annotations, the description covers purpose, edge-case behavior and the downstream tool. There is no material gap an agent would need filled before calling it.

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 the four-digit format, the 1958 boundary and the current-season default. The description mostly restates that, adding no new syntax or format nuance, so the baseline 3 applies.

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 specific verb and resource ('Get one Formula 1 season's constructors' championship table') and enumerates the returned fields (position, team, points, team profile slug). The word 'constructors'' cleanly separates it from the driver-standings sibling without needing to name it.

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 gives concrete usage conditions: pass season in four-digit form, expect an explicitly empty table for pre-1958 seasons, and feed the returned slug into formula1_team. It stops short of explicitly contrasting with formula1_driver_standings, but the constructors' framing and the follow-up routing make the intended call context clear.

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