Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

f1: Get circuits

f1_get_circuits
Read-onlyIdempotent

List Formula 1 circuits by season or all-time, with names, locations, and coordinates.

Instructions

List Formula 1 circuits for a given season or all-time. Returns circuit names, locations, and coordinates.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default 30, max 1000)
fieldsNoKeys to keep (comma-separated).
offsetNoNumber of results to skip for pagination
seasonNoSeason year (e.g. "2024") or "current" (default: "current")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
    • removedInput schema / properties / offset / maximum
      Removed value: -9007199254740991
  2. Changed2 schema fields changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  3. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the bar is lower. The description usefully names the returned fields (names, locations, coordinates), which matters since there is no output schema, but it says nothing about pagination or the default-limited result set that the params imply.

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?

Two tight sentences with zero waste; the scoping condition is front-loaded and the return summary follows. Nothing is redundant or padded.

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?

For a read-only list tool with full schema coverage and no output schema, the description covers purpose, scope, and return fields. It omits pagination behavior, but the schema carries that, leaving only minor gaps an agent can fill.

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 description coverage is 100%, so limit, fields, offset, and season are already documented in the schema; baseline is 3. The description only echoes the season concept and adds no syntax or format detail beyond what the schema provides.

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?

States a specific verb (list) and resource (Formula 1 circuits) with scope qualifiers (given season or all-time). The resource itself cleanly distinguishes it from siblings like f1_get_drivers or f1_get_constructors, though it does not explicitly name or contrast those neighbors.

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?

'For a given season or all-time' implies the usage context, but there is no explicit when-to-use or when-not guidance, and no alternative sibling is named. It is implied usage rather than a routing instruction.

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