Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

list_users

Retrieve amoCRM users and managers with IDs, names, roles, and groups to resolve responsible_user_id and created_by; optionally include deactivated users.

Instructions

List amoCRM users (managers) with IDs, names, roles and groups. Use to resolve responsible_user_id and created_by.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_inactiveNoInclude deactivated users (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the shape of the returned records (IDs, names, roles, groups) and that deactivated users may be excluded by default, which is genuinely useful. It says nothing about result size, pagination, or whether the full user roster is always returned, which matters for an unannotated list tool.

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 first states what is returned, the second states the use case. The most decision-relevant information is front-loaded.

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, single-optional-parameter read tool with no output schema, describing the returned fields fills the main gap an agent would face. The only missing piece is volume/pagination behavior, a minor omission 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 description coverage is 100% and the single optional parameter include_inactive is documented in the schema with its default. The description adds no further meaning about that flag, so the baseline of 3 applies — the schema does all the parameter work.

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 ('List') plus the resource ('amoCRM users (managers)') and even names the returned fields: IDs, names, roles and groups. That distinguishes it clearly from the other list_* siblings, which cover different resources. It stops short of an explicit contrast statement, but the resource noun does the differentiating work.

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

Usage Guidelines4/5

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

'Use to resolve responsible_user_id and created_by' is a concrete, actionable use case that tells an agent exactly when to reach for this tool rather than guessing. There are no exclusions or named alternatives, which is acceptable for a narrow lookup tool, but it keeps this out of the top band.

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