Skip to main content
Glama

message_mediator

Message mediator: rewrites a tense message between two people (e.g. separated parents) in a calm, neutral tone keeping the facts, with a title and the commitment to put in the calendar. AI model cost included in the price; nothing stored. Price: $0.02 USDC per call (x402).

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
langNo
textYesThe message to rewrite (max 1500 characters)
todayNo
childrenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose useful traits: nothing is stored, the AI cost is bundled, and payment is $0.02 USDC via x402 with the model cost included. It does not state error behavior, length limits (1500 chars only appears in the schema), how the calendar commitment is produced, or whether the rewrite is deterministic.

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?

It is two sentences: a dense but front-loaded functional description followed by a necessary pricing and privacy note. Every clause carries information (tone, facts preserved, outputs, storage, price), and there is no filler.

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

Completeness2/5

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

For a paid tool with six parameters, no output schema, and no annotations, the definition is thin where it matters most — five parameters are undocumented and the output shape (title, calendar commitment) is described only in prose. Privacy and cost are covered, but an agent still cannot confidently populate to, from, lang, today, or children.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 17% — just 'text' is documented in the schema — and five of the six parameters (to, from, lang enum same/it/en, today, children) get no explanation in the description. The mention of 'a title and the commitment to put in the calendar' hints that date and child names may drive outputs, but this is never tied to those parameters, so the meaning must be guessed.

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 names a specific verb and resource ('rewrites a tense message'), states the target tone ('calm, neutral'), the constraint ('keeping the facts'), and the extra outputs (a title and a calendar commitment). It is clear what the tool does, but it never distinguishes itself from the sibling message_tension_check, so an agent must infer the difference.

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

Usage Guidelines3/5

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

Usage is implied through the scenario ('tense message between two people, e.g. separated parents'), which tells the agent roughly when it applies. However, there is no explicit when-to-use, when-not-to-use, or routing guidance against message_tension_check or any other sibling, so the selection decision is left to inference.

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