Skip to main content
Glama
Sign In
f1verse MCP Server

f1verse MCP Server

by jinsim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Every Formula 1 venue recorded in the historical results.

f1_circuit_directory
Read-onlyIdempotent

Discover every Formula 1 circuit recorded in historical results, with source-labelled IDs, locations, and coordinates for venue history and event layout lookups.

Instructions

Every Formula 1 venue recorded in the historical results. A source-labelled directory of circuit ids, names, cities, countries and coordinates from 1950 to today. This is the discovery call for a historic venue; pass its id to f1_circuit_history for results, and use f1_circuit_profile with a year and round when the question needs that event's specific layout.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds useful context beyond that: the directory is source-labelled and spans 1950 to today, and it takes no filters, implying the full list is returned. It does not say anything about result size or whether the list can be narrowed, which is the one remaining behavioral gap.

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 the tool is and immediately followed by what it returns and where to go next. No filler and no repetition of the title.

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?

With an output schema present, the description does not need to enumerate return values, yet it still names the fields, and the downstream routing is fully spelled out. The only thing an agent might want and does not get is a sense of the result volume for a full 1950-to-present venue list.

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?

There are zero parameters, so the baseline is 4. The description still adds value by making clear the call is unfiltered and that the id it yields is the input key for the sibling tools, which is meaningful semantics for a lookup endpoint.

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 resource (a directory of every F1 venue in the historical results) plus the fields returned (ids, names, cities, countries, coordinates) and the 1950-to-today scope. It is clearly distinguishable from f1_circuit_history and f1_circuit_profile, which are named in the same breath.

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

Usage Guidelines5/5

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

Explicitly frames itself as the discovery call and gives the routing rule: take the id to f1_circuit_history for results, or go to f1_circuit_profile with a year and round when the question is about a specific event's layout. Both alternatives come with the condition that selects them.

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