Skip to main content
Glama

Tommos

Read a contact

get_contact
Read-onlyIdempotent

Fetch a single contact by id, with the figures (enrichment) and the note (company_note) of the company record the contact belongs to; both are null for a contact of no company. Pass include_deleted:true to resolve an archived contact (e.g. one a booking still references).

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
idYesRow id (uuid)
include_deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 covered. The description adds genuinely non-obvious behavior: the response is augmented with the parent company's enrichment figures and note, both null for company-less contacts, and archived records are invisible unless include_deleted is set — something no annotation conveys.

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 sentences, front-loaded with the core operation and then the parameter caveat, with no filler. The parenthetical naming of enrichment/company_note is slightly dense but earns its place by tying the note to the company record rather than the contact.

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?

With no output schema, the description carries the whole burden of describing returns, and it only characterizes the two company-derived fields — the contact's own returned fields and the not-found/archived-id failure behavior are left unstated. Adequate for a simple two-parameter read, but not fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% (id is documented as a uuid; include_deleted has no schema description), so the description must compensate. It does explain include_deleted's semantics — archived-row resolution — while the id format is left to the schema; the default (false) behavior of include_deleted is only implied, not stated.

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?

The description gives a specific verb and resource ("Fetch a single contact by id") and states the extra payload that comes back (the company's figures/enrichment and company_note). It is clearly a single-record read, distinguishable from create_contact/update_contact/delete_contact by the verb, but it never names a sibling (e.g., get_company for the company alone) to sharpen routing.

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

Usage Guidelines4/5

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

It gives a concrete conditional: pass include_deleted:true when you need to resolve an archived contact, with the motivating example of a booking that still references it. That is clear when-to-use guidance for the non-obvious parameter, though there are no explicit "when not to use" or alternative-tool cues.

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.