Skip to main content
Glama

HonestCRM

Update a company

update_company
DestructiveIdempotent

Change fields of a company. Send only the fields to change.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the company.
nameNoCompany name.
customNoCustom field values as an object of custom field id to value.
domainNoWebsite, such as example.com. The scheme and www are removed.
phonesNoPhone numbers. The first one is the primary number.
addressNoPostal address as free text.
descriptionNoWhat the company does, or notes about it.
ownerUserIdNoThe id of the user who owns the company. Default: the signed-in user.
leadSourceIdNoThe id of the lead source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the meaningful PATCH-style contract (only send changed fields), but it omits a key behavioral detail supported by the schema: several fields accept null, so an agent is not told whether passing null clears a value, and destructiveHint=true is never explained in terms of what can be lost.

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?

Two short sentences with no filler; the operative constraint about sending only changed fields is front-loaded right after the purpose. Nothing is repeated from the schema or annotations.

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

Completeness3/5

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

With nine parameters, a nested custom object, and full schema coverage, the description gives enough to make a basic call, and no output schema means return values needn't be explained. The gap is that null-to-clear semantics and the meaning of destructiveHint=true for an entity update are left unaddressed, which matters for an agent editing live data.

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%, including the nested custom-field object and the nullability of domain, address, description, ownerUserId, and leadSourceId, so the schema carries parameter meaning. The description only adds the omission semantics (unmentioned fields are untouched), which is a marginal but real addition over the schema.

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?

"Change fields of a company" gives a specific verb and resource, so an agent can immediately tell this mutates an existing company record rather than creating or fetching one. It does not distinguish itself from siblings like update_contact or update_deal, relying on the resource noun alone.

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

Usage Guidelines3/5

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

"Send only the fields to change" is a useful partial-update instruction that implies this is the tool to reach for when modifying a subset of an existing company's fields. However, there is no explicit statement of when to prefer create_company versus this, no prerequisites, and no note about whether omitted fields are preserved.

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