Skip to main content
Glama

AutoTasker Hub — China Social Data API

openf1

Formula 1 live session data: drivers, teams, numbers, headshots (OpenF1). $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 burden; it does add genuinely useful behavior in disclosing a price ($0.01 USDC), which tells the agent this is a paid call. It does not explain payment mechanics, whether credentials are needed, rate limits, or that results are limited to an active/live session.

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?

A single front-loaded line that identifies the domain, the payload, the upstream source, and the cost with no filler. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema tool, the description is minimally sufficient: it says what data comes back and at what price. It omits what an agent most needs to know operationally — whether a session must be live, what happens outside a race weekend, and how the micropayment is settled.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; baseline 4 applies. The description does not introduce any phantom inputs, which keeps it consistent with the empty schema.

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?

Names a specific resource domain (Formula 1 live session data) and enumerates the content types returned (drivers, teams, numbers, headshots), with the upstream source (OpenF1) identified. The verb is only implied ('data'), but no sibling in the catalog covers motorsport, so it is unmistakable against its neighbors.

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

Usage Guidelines2/5

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

There is no statement of when to call it, no prerequisites, and no mention of alternatives or when the data is unavailable. An agent must infer that any F1 request maps here, and knows nothing about whether it covers only live sessions or historical ones.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.