Skip to main content
Glama

Outil.io

Report reply

report_reply

Inscrire une réponse lue dans le navigateur (LinkedIn, Instagram, Facebook, TikTok) ou reçue par téléphone : {prospectId|contactId|outreachId, platform, text, intent facultatif, externalId pour éviter les doublons}. Mêmes effets qu’une réponse e-mail : la relance est annulée, stop exclut le prospect, interested crée l’opportunité.

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": {
      "platform": "<platform>",
      "text": "<text>"
    },
    "name": "report_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNo
textYes
intentNo
subjectNo
platformYes
contactIdNo
externalIdNo
outreachIdNo
prospectIdNo
receivedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare it is a non-destructive write; the description goes well beyond them by spelling out the domain consequences: the follow-up sequence is cancelled, a 'stop' intent excludes the prospect, and 'interested' creates an opportunity. It also explains that externalId exists to avoid duplicates, which is genuine behavioral context an agent could not infer.

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 dense sentences: the operation and its inputs first, the side effects second. The brace-list notation packs a lot in, though it reads as terse shorthand and the required-vs-optional distinction is only partially conveyed ('intent facultatif').

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 10-parameter mutation with no output schema and only minimal annotations, the definition covers the important ground: what to record, how to identify the target, dedup, and the downstream consequences. The remaining gap is the undocumented identity/subject/timestamp parameters, which force an agent to guess.

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 0%, so the description carries the burden; it identifies the identity triple (prospectId|contactId|outreachId), platform, text, optional intent and the dedup purpose of externalId. It says nothing about from, subject, receivedAt, or the meaning of the individual intent enum values beyond the two special cases (stop, interested).

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 opens with a specific verb+object ('Inscrire une réponse') and scopes it to replies read in a browser (LinkedIn, Instagram, Facebook, TikTok) or received by phone, which makes the operation unmistakable. It does not name or differentiate itself from the closest sibling (set_reply_intent), so it falls short of a 5.

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 clear situational context for when to call it: a reply has been observed on a social channel or by phone and needs to be recorded. The reference to 'Mêmes effets qu'une réponse e-mail' frames it against the email reply path, but no explicit exclusion or named alternative is offered.

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.