Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

motogp: Get session classification

motogp_get_session_classification
Read-onlyIdempotent

Retrieve full MotoGP session classification by session ID, including rider, team, constructor, time or gap, and points.

Instructions

Get the full classification (results) of a session: rider, team, constructor, time/gap and points. Use a session id from motogp_get_sessions.

Input Schema

NameRequiredDescriptionDefault
testNoSet true for test sessions (default false)
fieldsNoKeys to keep (comma-separated).
session_idYesSession id from motogp_get_sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
+}
  2. Addedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, covering the safety profile without any help from the description. The description adds the shape of the payload (rider/team/constructor/time-gap/points) but says nothing about pagination, whether 'full' means unpaginated, or how test sessions change behavior. No contradiction with annotations.

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 short sentences: the first front-loads what is returned, the second front-loads the input requirement. No filler, no restatement of the tool name or 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 no output schema, the field enumeration in the description usefully tells the agent what comes back, and the input provenance is covered. It is slightly incomplete on the two optional parameters (test, fields) and on pagination/limits for a 'full' classification, but nothing essential for a correct call is missing.

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 all three parameters (session_id, test, fields) are documented in the schema itself; baseline 3 applies. The description only reinforces the session_id provenance already stated in the schema and says nothing about the `test` flag or the `fields` projection, adding no meaning beyond it.

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 verb ('Get') and resource ('full classification (results) of a session') and enumerates the returned fields (rider, team, constructor, time/gap, points). This clearly distinguishes it from siblings such as motogp_get_standings or motogp_get_sessions, which return season-level or session-list data rather than a single session's result order.

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?

Gives a concrete precondition and routes the agent to the sibling that supplies the required input: 'Use a session id from motogp_get_sessions.' That is real usage guidance, but there is no when-not guidance or mention of how this differs from standings/classification-style siblings beyond the id requirement.

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