Skip to main content
Glama

HonestCRM

Get a contact

get_contact
Read-onlyIdempotent

Read one contact with its company, open deals, open tasks and last 5 activities.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the contact.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuine value by disclosing the response payload composition, notably that only the last 5 activities and only open deals/tasks are included. It does not say what happens when the id is unknown (empty vs. error), which is the main remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with zero filler, and the payload contents are front-loaded so an agent learns immediately what comes back. Nothing is wasted, though the sentence could be tightened slightly.

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?

For a single read-only lookup with no output schema, the description does the important work of sketching the returned shape. It is still missing error/not-found behavior and whether the nested collections are truncated or filterable, which matters given the explicit 'last 5' and 'open only' limits.

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?

There is a single parameter with 100% schema description coverage, so the schema fully documents the id including its UUID format and pattern. The description adds no meaning beyond that, which is the baseline expectation at this coverage level.

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 ('Read one contact') and enumerates the related data bundled in the response (company, open deals, open tasks, last 5 activities), which separates it from get_company and get_deal by resource. It stops short of explicitly contrasting itself with the list/search siblings, so it is clear rather than exemplary.

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?

Usage is only implied: 'one contact' plus a required id signals single-record retrieval as opposed to listing or searching. There is no explicit when-to-use, no named alternative (e.g., search for looking up a contact by name), and no stated prerequisite such as needing a known id.

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