Skip to main content
Glama

message_tension_check

Tension check before sending: how conflictual a message is (0-100), why, and how to make it calmer. AI model cost included; nothing stored. Price: $0.01 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_tension_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
textYesThe message to check (max 1500 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does so better than average: it discloses the x402 payment requirement and exact price ($0.01 USDC per call), that the AI model cost is included, and that nothing is stored. It omits rate limits, failure behavior for oversized input, and latency, which keeps it from a 5.

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?

The most decision-relevant facts — what it returns and when to use it — are front-loaded, followed by retention and pricing details in terse clauses. Three fragments carry a lot without filler, though the pricing sentence is somewhat dense with parenthetical jargon (x402).

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, and the description does explain the return shape (score, rationale, calmer alternative), so an agent knows what to expect. Combined with the cost and no-storage disclosures, the definition is nearly complete for a two-parameter tool; only the lang parameter's semantics remain unspecified.

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 50%: the text parameter is documented in the schema with a 1500-character cap, but the lang parameter (enum same/it/en) is cryptic and left entirely unexplained by the description — an agent cannot tell what 'same' vs. 'it'/'en' means. The description adds no parameter meaning beyond the schema, so it neither compensates for the gap nor leaves it fully opaque.

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 states a specific action (tension check on a message before sending) and the return content precisely: a 0-100 conflict score, the reasoning, and calmer rewrites. It is clear what the tool does, but it does not distinguish itself from the sibling message_mediator, which an agent could plausibly confuse it with.

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 phrase 'before sending' supplies a clear usage context, telling the agent this is a pre-send check rather than a post-hoc analysis. There are no explicit exclusions and no named alternative for cases where the agent wants mediation or rewriting instead, so the routing guidance stops short of full coverage.

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