Skip to main content
Glama

Contact (CRM)

crm_get_contact
Read-onlyIdempotent

One person: identity, provenance, gap state, the activity that touched them.

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": {
      "contact_id": "<contact_id>"
    },
    "name": "crm_get_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idYesThe contact, e.g. P-0001.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 the safety profile is fully covered. The description adds genuine content beyond that by naming the returned facets — provenance, gap state, and linked activity — which hints at non-obvious composite behavior. However, with no output schema, terms like "gap state" and "provenance" are left undefined.

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 short sentence with no padding, and the subject (single person) is front-loaded. It is arguably over-compressed, using jargon labels instead of plain language, but there is no wasted text.

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-parameter read tool, annotations cover safety and the schema covers the parameter, so the essentials are present. With no output schema, though, the description is the only source for return-value expectations and it delivers only a cryptic list of facets rather than explaining what the agent will actually receive.

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 contact_id parameter is documented with an example (P-0001). The description adds no format, validation, or lookup-failure information beyond what the schema already provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"One person" plus the enumerated facets (identity, provenance, gap state, activity) tells the agent this returns a single contact record, which implicitly contrasts with crm_list_contacts. But it is a noun phrase with no verb — it never says "fetch/retrieve by contact_id" — so the actual operation must be inferred from the tool name rather than the description.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus crm_list_contacts, crm_get_account, crm_gaps, or crm_update_contact. The singular framing implies single-record lookup, but no explicit routing or prerequisites are given.

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.