Skip to main content
Glama

companies_update_company

Destructive

Update an existing company record by ID, including legal registration, banking, address details, and linked document file IDs, so incorrect or changed company information can be corrected.

Instructions

Update company PATCH /companies/{id}

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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "companies_update_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCompany ID
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the description must add context — but it adds none. It does not say whether this is a partial or full replacement (PATCH with a required legal sub-object is ambiguous), whether omitted fields are cleared, or what permissions are needed. It also does not contradict the annotations.

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

Conciseness2/5

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

It is short, but it is under-specified rather than concise: a bare imperative plus an HTTP route. There is no front-loaded statement of effect, scope, or return behavior to anchor the reader.

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

Completeness1/5

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

For a destructive, non-idempotent mutation with a nested required sub-object, no output schema, and half the parameters undocumented, this definition leaves the agent without the information needed to call it safely. Nothing about overwrite semantics, error behavior, or authorization is provided.

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

Parameters1/5

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

Schema description coverage is only 50%, and the description contributes nothing about the two required parameters. In particular, the nested body.legal object with seven required fields (name, inn, bik, account, ogrn, address, corrAccount) and the documentFileIds array are left entirely unexplained, so the agent cannot know whether supplying legal overwrites existing legal data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update company" plus the raw endpoint PATCH /companies/{id} essentially restates the tool name (companies_update_company) rather than describing what aspects of a company are updated. There is no differentiation from siblings such as companies_create or accounts_patch_account_me beyond the HTTP verb.

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

Usage Guidelines1/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives. The only routing signal an agent gets is the endpoint path, which is not an instruction about when this call is appropriate versus creating or reading a company.

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