Skip to main content
Glama

A contact's message history

contact_timeline
Read-onlyIdempotent

The messages exchanged with one contact on a given channel, newest first. 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_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page number, default 0
sizeNoPage size, default 50, max 200
channelNoDefault "whatsapp"
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Read only' merely restates structured data. The one genuinely additive behavioral fact is the newest-first ordering, which tells the agent how results are sequenced. Pagination behavior and what an empty/invalid contact yields are still undisclosed.

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, front-loaded with the subject and ordering. The trailing 'Read only.' is the only wasted clause since the annotation already asserts it, but the text is otherwise tight.

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?

A simple read tool with fully documented parameters and strong annotations needs little more, and ordering is covered. However, with no output schema the description could have sketched the returned message fields or pagination semantics and does not.

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 page, size, channel (with its 'whatsapp' default) and contactId are all documented in the schema. The description only restates the contact/channel scoping at a high level and adds no format, ID-source, or validation detail. Baseline 3 applies.

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 names the resource precisely: messages exchanged with one contact on a given channel, plus the ordering (newest first). It does not invoke sibling tool names to differentiate itself (e.g., from call_transcript or contact_detail), and it reads as a noun phrase rather than a verb, but an agent can still tell what it returns.

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 when-to-use guidance, no exclusion of alternatives, and no stated prerequisites (e.g., that a valid contactId is needed or how this differs from fetching a single message status). The agent must infer the call context entirely.

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.