Skip to main content
Glama

Outil.io

Set reply intent

set_reply_intent

Confirmer ou corriger l’intention d’une réponse (id de list_replies). stop : exclusion du prospect (exclude_prospect), contact désabonné, adresse bloquée ; interested : opportunité créée une seule fois dans le pipeline Prospection (étape Intéressé) et événement de workflow prospect.interested ; later : relance du prospect dans 30 jours ; not_interested : plus de relance ; question : relance immédiate. handled:true marque la réponse traitée.

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>",
      "intent": "<intent>"
    },
    "name": "set_reply_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
intentYes
handledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare a non-readonly, non-open-world, non-destructive write, so the description carries most of the burden — and it delivers real consequences per intent (pipeline opportunity creation, prospect.interested workflow event, prospect exclusion, 30-day follow-up scheduling, immediate follow-up). It even discloses idempotency for one branch ('opportunité créée une seule fois'), which annotations could never convey. Gaps remain: whether the exclusion for 'stop' is reversible, and whether re-calling with a different intent replaces the prior side effects.

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?

Purpose is front-loaded in the first clause, then consequences are packed into a single semicolon-delimited enumeration that matches one-to-one with the enum values — efficient for six intents. It is a dense run-on rather than structured bullets, which costs a little scanability, but no sentence is padding.

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 would ideally say what comes back; it does not. But for an idempotency-sensitive mutation tool with three params, it covers the decisive information: source of the id, side effect per intent, and the single-creation guarantee for 'interested'. The undocumented 'unclassified' branch and absent return-value note are the remaining holes.

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%, so the description must compensate, and it does for the highest-risk parameter: five of the six intent enum values are given operational meaning (stop, interested, later, not_interested, question). It also explains 'handled:true'. It falls short on 'unclassified' (in the enum but never described) and on what handled:false means or defaults to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('confirmer ou corriger l'intention d'une réponse') and immediately anchors the resource to its source ('id de list_replies'), so the agent knows the object being modified and where its identifier comes from. It also names concrete sibling-level consequences ('exclusion du prospect (exclude_prospect)'), which separates this tool from both the listing tool and the exclusion tool without needing the schema.

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?

The prerequisite context is explicit: the id must come from list_replies, so the agent knows this is a second-step call after reading replies. However, there is no explicit statement of when NOT to use it (e.g. calling exclude_prospect directly, or using report_reply instead), so the routing is clear but not fully closed.

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.