Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

get_company

Retrieve a single company by ID with its custom fields; optionally embed linked leads, contacts, or customers using the 'with' parameter.

Instructions

Get a single company by ID with custom fields. Use 'with' to embed linked leads and contacts.

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": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
withNoRelated entities to embed
company_idYesCompany ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully states that custom fields are returned and that 'with' embeds linked entities, but says nothing about permissions, behavior when the ID is unknown, or whether embedded results are paginated or truncated.

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 core operation is front-loaded and the optional-embedding hint follows immediately.

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

Completeness4/5

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

For a simple two-parameter read tool with full schema documentation and no output schema, the description covers the operation and the notable response feature (custom fields, embeds). Only error/auth behavior is left unstated, which is a minor gap at this complexity level.

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 coverage is 100%, so both parameters are already documented, setting a baseline of 3. The description adds only that 'with' is used to embed lead and contact records, and notably omits 'customers' which is present in the enum, so it adds partial and slightly incomplete meaning.

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?

States a specific verb and resource ('Get a single company by ID') and signals singular retrieval, which contrasts implicitly with list_companies. It does not name a sibling explicitly, so differentiation relies on inference from the word 'single'.

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?

The description implies the use case (fetch a known company by ID) and gives guidance on the optional 'with' parameter for embedding, but offers no explicit when-to-use vs when-not-to-use framing or pointer to list_companies/search for discovery scenarios.

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