aidoo-mcp-server

aidoo_update_member

Update a member's contact information and personal details in Aidoo fitness studio management by specifying the member ID and optional fields.

Instructions

Aktualisiere ein bestehendes Mitglied.

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": {
      "member_id": "<member_id>"
    },
    "name": "aidoo_update_member"
  }
}

Input Schema

Name	Required	Description
`zip`	No	Postleitzahl
`city`	No	Stadt
`email`	No	E-Mail-Adresse
`phone`	No	Telefonnummer
`street`	No	Straße und Hausnummer
`lastname`	No	Nachname
`firstname`	No	Vorname
`member_id`	Yes	Mitglieds-ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'update an existing member.' It does not explain partial update semantics, permission requirements, return values, or what happens to unspecified fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a concise single sentence with no unnecessary words, making it easy to parse. However, it is so brief that it omits important behavioral details, which slightly reduces its structural value.

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?

For a mutation tool with no annotations and no output schema, the description is critically incomplete. It fails to disclose update behavior, side effects, or return values, leaving the agent with insufficient context for correct invocation.

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 provides 100% coverage for all 8 parameters with descriptive names and descriptions, so the baseline is 3. The tool description adds no extra parameter semantics beyond what the schema already offers.

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?

The description clearly states the action ('update') and resource ('existing member'), which distinguishes it from sibling tools like create, get, or list member. However, it lacks any additional context or scope beyond the basic action.

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 such as aidoo_create_member or aidoo_get_member. It does not mention prerequisites, exclusions, or typical use cases.

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