Retrieve a single address by ID from Accelo CRM, including optional fields such as country and state, for accurate contact or company address lookups.
Get a single address by ID.
Args: id: Address ID fields: Additional fields to return, e.g. "country(),state()"
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| fields | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Get' implies a read operation, but it does not disclose permissions, error behavior, side effects, or return behavior.
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?
The description is brief and front-loaded, stating the core action first and then the args without wasted wording.
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 simple get-by-ID tool the input basics are covered, but with no annotations and no output schema the description omits return shape, default fields, and failure behavior.
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?
Schema description coverage is 0%, so the description must compensate. It documents both id as the address ID and fields as additional fields to return, including example syntax 'country(),state()', though it lacks deeper constraints.
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?
The description states a specific verb and resource: 'Get a single address by ID.' This clearly distinguishes retrieval of one address from sibling operations like accelo_list_addresses and accelo_count_addresses.
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?
No guidance is provided on when to use this tool versus alternatives such as accelo_list_addresses. The intended usage is only implied by 'by ID'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.