Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

update_company

Modify an existing company by ID, changing its name, responsible user, or custom field values to keep CRM records accurate.

Instructions

Update an existing company: name, responsible user, or custom fields.

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_id": "<company_id>"
    },
    "name": "update_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew company name
company_idYesCompany ID to update
responsible_user_idNoNew responsible user ID
custom_fields_valuesNoCustom field values to set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does little beyond implying a mutation. It never states whether this is a partial/merge update (only supplied fields change) or a full replacement, whether custom_fields_values appends or overwrites existing fields, what permissions or auth are needed, or what happens if company_id does not exist.

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?

A single front-loaded sentence with a clear verb-resource-field structure and zero filler. Nothing could be removed without losing information.

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 four parameters, no annotations, and no output schema, the description is too thin. Partial-update semantics, nested custom_fields_values behavior, permission requirements, and failure modes are all left undocumented, so an agent cannot confidently predict the effect of a call.

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?

Schema description coverage is 100%, so every parameter already has its own documentation, making 3 the baseline. The description mirrors the schema by listing name, responsible user, and custom fields but adds no syntax, format, or merge-semantics detail beyond it.

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 gives a specific verb ('Update') and resource ('an existing company') and enumerates the mutable surfaces: name, responsible user, custom fields. It is clearly distinguishable from create_company or get_company by the verb and the word 'existing', though it never names a sibling explicitly.

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?

There is no explicit guidance about when to choose this tool over the alternatives (e.g. create_company vs update_contact for a person, or whether to call get_company first). The word 'existing' weakly implies the company must already exist, but no prerequisites, exclusions, or alternative-routing advice are stated.

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