Skip to main content
Glama

Get one contact

contact_detail
Read-onlyIdempotent

Everything on file for one contact by its contact id. Read only.

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": {
      "contactId": "<contactId>"
    },
    "name": "contact_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactIdYesThe contact's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / contactId / description
      Previous value: -"The contact id, as returned by contact_list or contact_search"New value: +"The contact's id"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds only the return-scope hint 'everything on file' and redundantly repeats 'read only'; it does not describe auth needs, not-found behavior, rate limits, or specific fields.

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?

Two short sentences, with the purpose front-loaded and minimal waste. The second sentence is largely redundant with the readOnly annotation, but the description remains efficient.

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?

This is a simple one-parameter read tool with rich annotations and complete schema coverage for the parameter. The description is sufficient to invoke it, but it remains vague about what 'everything on file' returns and what happens when the contact ID is missing or invalid.

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 one required parameter and the schema already describes it fully. The description restates 'contact id' but adds no format, validation, or sourcing guidance, so it meets the baseline for high schema coverage.

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 that it retrieves everything on file for one contact by contactId, which is a clear single-record fetch. It does not explicitly contrast itself with siblings such as contact_by_phone, contact_search, or contact_list.

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?

The phrase 'by its contact id' implies the tool should be used when the contact ID is already known. However, there is no explicit when-to-use guidance or routing to alternatives like contact_search or contact_by_phone.

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.