Skip to main content
Glama
Sign In

Ficiel MCP

by io.ficiel
OverviewDiscussionsAdmin

Simuler une réponse (SANS envoi)

ficiel_simulate_reply
Read-only

AUCUN MESSAGE N'EST ENVOYÉ. Simule ce que Kord répondrait sur une conversation, avec l'identité, le ton et les règles apprises de votre organisation, et rend le texte pour relecture uniquement. Approximation, pas une reproduction exacte du bouton « Suggérer » de l'interface (moteur partagé, réglages fins différents). Consomme le même quota mensuel de conversations traitées par l'IA que toute génération réelle.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "ficiel_simulate_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversation_idYesIdentifiant de la conversation (conversation_id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/destructiveHint annotations, it discloses that no message is sent, that it consumes the same monthly AI-processed-conversation quota as a real generation, and that output is an approximation with different fine-tuning than the UI button. The quota note is a genuinely useful behavioral trait not captured by any annotation.

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?

Front-loaded with the critical constraint 'AUCUN MESSAGE N'EST ENVOYÉ' in caps, followed by two tight sentences covering behavior, caveat, and cost. Every sentence earns its place with no filler.

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

Completeness5/5

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

For a single-parameter, read-only, non-open-world tool with no output schema, the description covers what it does, that nothing is sent, the approximation caveat, and the quota cost. Nothing needed to invoke it correctly is missing.

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?

There is a single parameter (conversation_id) with 100% schema description coverage, so the schema already carries the semantics. The description adds no format, scope, or validity detail beyond what the schema provides, matching the baseline 3 for fully-documented params.

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 (simulate/render for review) and resource (a reply on a conversation) and explicitly differentiates from real sending with 'AUCUN MESSAGE N'EST ENVOYÉ'. It also distinguishes itself from the UI 'Suggérer' button, so an agent can tell it apart from siblings like ficiel_send_message.

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 clearly frames the context — use this to preview text for review only, nothing is dispatched — which implies the alternative (real send tools). However, it never names a sibling (e.g. ficiel_send_message) or states an explicit when-not-to-use condition, so routing is inferred 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.

All Ficiel MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources