Skip to main content
Glama

Escribir a mi gestor

gestoria_send_message
DestructiveIdempotent

Use this when a connected Kuotia gestoría client explicitly asks to send a text message to their gestor (a question, a heads-up, a reply). It sends exactly the text the client approved, as the client, to their own gestor in the Kuotia portal, where the gestor answers; it cannot be unsent. Show the final text and get the client's confirmation before calling. Recommend sending documents, identity numbers (DNI, NIF, NIE) and bank details through the Kuotia portal instead of this message; the text is sent as the client writes it. No attachments, and it never reads messages back. Reuse the same idempotency_key when retrying the same message. Do not use for questions general tools answer.

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": {
      "body": "<body>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "gestoria_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe exact text to send.
topicNootro
subjectNoSubject, only when starting a new conversation.
idempotency_keyYesA new random UUID (for example 0f8fad5b-d9cb-469f-a165-70867728950e) for each action. Reuse exactly the same UUID only when retrying the same action.
new_conversationNoStart a new conversation instead of writing in the latest open one.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the action cannot be unsent, that the text is sent verbatim as the client writes it, that there are no attachments, that it never reads messages back, and that retries must reuse the same idempotency_key. This is consistent with destructiveHint=true and idempotentHint=true rather than contradicting them.

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?

Front-loaded with the triggering condition and dense with actionable constraints. Some redundancy exists — 'exactly the text the client approved' and 'as the client writes it' overlap, and the idempotency retry instruction restates the schema — but no sentence is wasted given the mutation risk.

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 destructive, 5-parameter send tool with an output schema already covering return values, the description supplies everything needed to call it correctly: confirmation gate, irreversibility, content constraints, retry semantics, and channel alternatives.

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 80%, so the schema already carries the parameter meaning (including the UUID pattern and the idempotency retry rule). The description reinforces that 'body' must be the exact approved text, but says nothing about topic, subject, or new_conversation, so it adds only marginal meaning beyond structured fields.

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?

States a specific verb and resource ('send a text message to their gestor') plus the exact actor/scope ('as the client, to their own gestor in the Kuotia portal'), and explicitly excludes general questions. An agent can distinguish it from the read-oriented siblings (obligations, tax status, requests) without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('when a connected Kuotia gestoría client explicitly asks'), a required flow (show final text, get confirmation), redirects to an alternative channel for documents, DNI/NIF/NIE and bank details, and states when not to use it ('Do not use for questions general tools answer').

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.

Resources