Skip to main content
Glama

Get one contact

get_contact
Read-only

Fetch a single contact with its recent activity timeline (calls, emails, notes, outreach). The timeline is capped and says so when it is truncated. A timeline row is NOT necessarily something the contact said. Rows derived from a lead carry body_author saying who wrote the body: a manually logged lead is your own team's internal note, a web chat is your assistant's summary, a call is your voice agent's summary. Every row reads direction=inbound regardless. Never quote a body back to the contact, and never write "you said" or "you mentioned" about one, unless body_author says the contact wrote it. Each row also carries latest_status: the delivery state (e.g. sent, delivered, bounced). A failure always outranks success, and engagement such as opened or clicked appears only in receipts, never in latest_status. When any exist, each row also carries receipts: dated status events as "status@time", oldest first, where "status~@time" means the time is approximate. Times are the provider's own time when it gave one, otherwise when we received the event. If a row has more than 20 receipts only the first 5 and last 15 are listed and receipts_omitted says how many were dropped. receipts_unavailable (top level) means receipts could not be read; no receipts are shown in that case.

Input Schema

NameRequiredDescriptionDefault
contact_idYesThe contact id
activity_limitNoTimeline rows, default 25, ceiling 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare read-only, non-destructive, closed-world behavior. The description adds substantial behavioral context beyond that: timeline truncation, body_author semantics, direction caveats, latest_status precedence, receipts formatting, and receipts_unavailable handling.

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?

The purpose is front-loaded in the first sentence, and the remaining sentences are dense but relevant to correct interpretation of the returned timeline. It could be more scannable, but there is little wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining return semantics, and it does so thoroughly for the activity timeline. It does not describe the contact object's own fields, but the timeline caveats are the main complexity and are well covered.

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%, so both contact_id and activity_limit are already documented in the schema. The description mentions that the timeline is capped but does not add parameter-level meaning beyond the schema's default and ceiling details.

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 states a specific verb and resource: "Fetch a single contact with its recent activity timeline." It implicitly distinguishes this from list/search siblings by saying "single contact," but it does not explicitly name alternatives such as list_contacts or search_contacts.

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 implied by the required contact_id and the single-contact framing, but the description never explicitly says when to use this tool versus list_contacts, search_contacts, or get_lead. The extensive guidance is about interpreting timeline rows, not about tool selection.

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