aidoo-mcp-server

aidoo_get_gym

Retrieve a fitness studio's full details using its gym ID. Access essential studio information from Aidoo for your management tasks.

Instructions

Rufe Details eines Studios ab.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gym_id": "<gym_id>"
    },
    "name": "aidoo_get_gym"
  }
}

Input Schema

Name	Required	Description	Default
`gym_id`	Yes	Studio-ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states that details are retrieved, without disclosing what 'details' include, whether a missing gym_id yields an error, or any access requirements. For a read tool, this is minimal information.

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?

The description is a single concise sentence that directly states the action. It is front-loaded and contains no filler, making it efficient for an agent to parse quickly.

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

Completeness2/5

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

The tool has no output schema, so the description should provide some insight into return values or behavior. The phrase 'Details eines Studios' is vague; it does not mention specific fields (e.g., address, contact info, hours) or error handling. Given the simple getter nature, a bit more context would be expected.

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?

The schema has one parameter with 100% coverage ('gym_id' described as 'Studio-ID'), so the schema already explains the parameter. The description adds no extra semantics beyond the schema's field label, which is expected per the 100% coverage baseline.

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 'Rufe Details eines Studios ab' ('Retrieve details of a studio') uses a specific verb ('Rufe ab' = retrieve) and resource ('Details eines Studios' = details of a studio). It clearly distinguishes from sibling tools like aidoo_list_gyms (listing) and aidoo_get_gym_statistics (statistics).

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it requires a gym_id obtained from aidoo_list_gyms, nor does it contrast with other gym-related tools. The usage context is only implied by the 'get' pattern.

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