Vitalli

vitalli_update_organization

DestructiveIdempotent

Update fields of an organization (only the given fields change). Address changes are re-geocoded.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "vitalli_update_organization"
  }
}

Input Schema

Name	Required	Description
`city`	No
`kind`	No
`name`	No
`tags`	No
`notes`	No
`street`	No
`country`	No	ISO country code, default DE
`website`	No
`mainEmail`	No
`mainPhone`	No
`postalCode`	No
`visibility`	No
`displayName`	No
`organizationId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds valuable semantics beyond annotations: partial update behavior ('only the given fields change') and a side effect ('Address changes are re-geocoded'). However, it does not explain what makes the operation destructive or mention permission requirements.

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 two compact sentences with no wasted words. The partial-update rule is front-loaded before the side-effect note. It is arguably too terse for a 14-parameter tool, but that is a completeness issue rather than verbosity.

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?

This is a complex mutation tool with 14 parameters, low schema coverage, and no output schema. The description omits parameter semantics, permission needs, validation behavior, and what makes it destructive, leaving significant gaps for an agent to call it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 14 parameters and only 7% schema description coverage, the description must compensate but does not. It only hints at address-related parameters via re-geocoding, leaving fields like 'kind', 'visibility', 'tags', and 'notes' undocumented in both schema and description.

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 states a specific verb and resource ('Update fields of an organization'), making the action clear. It does not explicitly differentiate from siblings like vitalli_create_organization or vitalli_get_organization, but the name and verb make the intent obvious.

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?

The description gives no guidance on when to use this tool versus alternatives, no prerequisites (e.g., fetching the organization first), and no mention of who can update. It only implies usage from the verb 'update'.

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

All Vitalli tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?