Skip to main content
Glama

Send to support

send_support_message
Destructive

Send to MONETEKA support the message that was previewed and whose exact text the user approved.

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": {
      "intent_id": "<intent_id>"
    },
    "name": "send_support_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
intent_idYesintent_id from prepare_moneteka_action, after the user saw its preview and agreed.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the irreversible external-send profile is largely covered structurally. The description adds useful confirmation that the payload is exactly the previewed text, but says nothing about failure behavior, retries, or whether the message can be recalled — a modest addition over the annotations.

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?

A single sentence with no filler; the action and the approval gate are front-loaded together so the agent can act immediately.

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?

With one required parameter, an output schema, and full annotation coverage, the definition supplies what an agent needs to call it correctly. Only edge-case behavior (failed send, already-consumed intent) is unaddressed, which is acceptable at this complexity.

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 coverage is 100% and the intent_id parameter description already specifies its provenance (from prepare_moneteka_action after user agreement). The description echoes that constraint rather than adding new meaning such as expiry, reuse rules, or what happens if the intent was already consumed.

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?

Names a specific verb and destination ("Send to MONETEKA support") and constrains it to the previewed, user-approved message. That framing tells an agent both what the tool does and that it is the terminal step of a preview/approve flow, setting it apart from prepare_moneteka_action.

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?

Implicitly and partly explicitly states the precondition: the message must have been previewed and approved by the user, and the intent_id must come from prepare_moneteka_action. It does not state when NOT to call it (e.g., if the preview was edited or rejected), so it stops short of full alternative guidance.

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