Skip to main content
Glama

Outil.io

Get contact conversation

get_contact_conversation
Read-only

Fil de conversation d’un contact du CRM, par son identifiant.

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": "get_contact_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered by structured data. Beyond that the description adds nothing: it does not say whether all messages are returned, whether the thread is ordered, whether an empty thread is possible, or what happens for a nonexistent contactId. Since annotations carry the read-only profile, the bar is lower, but the description still contributes no behavioral context.

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?

A single short sentence with no padding or redundant restatement of the title. It is efficiently front-loaded, but the sparseness is under-specification rather than genuine density.

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

Completeness2/5

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

For a tool that returns a whole conversation thread, the description says nothing about the response: order, pagination, message fields, or empty results. With no output schema, that burden falls entirely on the description, and it is not met.

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?

With one parameter and 0% schema description coverage, the description's phrase 'par son identifiant' plus the schema's 'contactId' (integer, exclusiveMinimum 0) roughly conveys the argument's meaning. It adds no detail on where the identifier comes from or whether it is the CRM contact ID versus an external ID, so the compensation is partial.

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 French phrase 'Fil de conversation d'un contact du CRM, par son identifiant' names the resource (a CRM contact's conversation thread) and the lookup key (the contact identifier). It is clearly a retrieval of one contact's thread, distinguishable from the broader 'get_conversation' sibling, though the wording is noun-phrase rather than a verb and leaves the exact payload shape implicit.

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 indication of when to call this versus get_conversation, link_conversation_contact, or get_contact_overview. The only guidance is implicit in the noun phrase 'par son identifiant', which tells the agent nothing about preconditions such as whether the contact must already have a conversation.

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.