Skip to main content
Glama

Update a company

company_update
Idempotent

Changes details of one of your companies (owners and admins): name, legal name, contact, address, registration numbers. Send only the fields to change inside patch. ifVersion must be the version from company_get; a stale version is refused. Changing the name or registration numbers of a verified company resets its verification. Logo upload is on the website. Call without confirm first for a preview, then again with confirm and the preview_token.

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": {
      "company": "<company>",
      "ifVersion": "<ifVersion>",
      "patch": "<patch>"
    },
    "name": "company_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYesOnly the fields to change.
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.
confirmNoSet true only on the second call, after the user approved the preview.
ifVersionYesThe version from company_get.
preview_tokenNoThe preview_token returned by the first call (same input).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, but the description adds genuinely non-obvious behavior: the two-step preview/confirm protocol, version-based optimistic concurrency, and the side effect that changing name or registration numbers resets verification of a verified company. That verification-reset side effect is a meaningful consequence not captured by destructiveHint=false, though it is disclosed rather than contradicted.

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?

Four dense sentences, front-loaded with the action and scope, then the patch rule, then the version rule, then the side effect and the preview flow. No filler and no repetition of schema content.

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

Completeness5/5

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

For a 5-parameter mutation with nested objects and no output schema, the description covers the mutation semantics, concurrency control, confirmation protocol, and the one surprising side effect. Nothing an agent needs to invoke it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: patch is a partial-update container, ifVersion must come from company_get and staleness is rejected, and confirm/preview_token form a two-call handshake. It does not restate the nested field constraints, which the schema already handles.

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 and resource ('Changes details of one of your companies') and enumerates the mutable field groups (name, legal name, contact, address, registration numbers). It also implicitly separates itself from company_get (the version source) and company_create, so an agent can route correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit operating instructions: send only changed fields in patch, obtain ifVersion from company_get, call once without confirm for a preview then again with confirm plus preview_token, and use the website for logo upload. It also names the audience constraint (owners and admins) and the failure condition (stale version refused).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources