Skip to main content
Glama

get_contact_history

Read-onlyIdempotent

Read a contact and their recent enquiries, notes and messages. Pass both cursor fields from next to read older history.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
beforeNo
cursorIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value with the pagination rule that both cursor fields must be passed together. It stays at 3 because it never explains what 'next' is, whether the default read is truncated, or how much history is returned initially.

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

Conciseness5/5

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

Two short, front-loaded sentences with zero filler. The primary action comes first and the pagination caveat second, which is the right priority order.

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?

For a simple three-parameter read with no output schema, the definition covers the action, the returned entities, and the follow-on pagination step. The remaining gap is the shape of the pagination token (where 'next' lives), which matters more here because no output schema documents it.

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 0% across three parameters, so the description has to carry the load. It does reasonably well: 'a contact' identifies the required id, and the second sentence explains that before and cursorId are a cursor pair drawn from the previous response. It loses a point because it never says which field is the time bound versus the opaque token, leaving the integer-versus-string split to the schema alone.

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?

A specific verb ('Read') plus a clearly scoped resource: the contact plus 'their recent enquiries, notes and messages'. That tells an agent exactly what comes back and how it differs from the mutation siblings (add_contact_note, update_contact_profile). It stops short of a 5 because it does not distinguish itself from lookalikes such as get_contact_follow_up_summary.

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?

Pagination guidance is explicit: pass both cursor fields from 'next' to read older history. But there is no guidance on when to choose this tool over get_contact_follow_up_summary or the per-domain history tools, and no prerequisites or exclusions. Usage is implied rather than spelled out.

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