Retrieve every CRM user eligible to own leads, contacts, accounts, or deals, with their owner_id. Use these IDs to assign records correctly.
List all CRM users who can own leads/contacts/accounts/deals, with their owner_id.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'List all' implies a read-only, unfiltered enumeration, but it does not disclose scope limits (active users only?), ordering, pagination, or permission requirements for a user-listing endpoint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One dense sentence with no waste; the resource and the payload ('with their owner_id') are both front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read tool with no output schema, the description adequately covers what is returned (CRM users plus their owner_id). It falls short only on behavioral details like return ordering or whether the list is scoped to active owners.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has zero parameters, so there is nothing for the schema to document and the baseline is 4. The description correctly implies the call takes no filters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List all CRM users who can own leads/contacts/accounts/deals') and even names the returned field (owner_id). It is clearly distinguishable from the CRUD siblings, though it doesn't explicitly contrast itself with any of them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: the mention of 'owner_id' hints this is the reference lookup you call before assigning owners on leads/contacts/etc., but there is no explicit when-to-use statement or pointer to the tools that consume owner_id (create_lead, update_deal, etc.).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.