Skip to main content
Glama

rewrite_inbox_reply

Read-only

Rewrite draft reply text for owner review using the approved business's Inbox AI settings.

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

Input Schema

NameRequiredDescriptionDefault
idYes
textYes
styleNopolish
instructionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds genuinely new context beyond that: rewriting derives from the business's approved Inbox AI settings, which implies configuration preconditions set up via the settings tools. It does not explain whether the rewritten text is persisted anywhere or purely returned, which is the one thing an agent would still want to know.

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?

A single tight sentence with no filler and the key qualifiers ("for owner review", "approved business's Inbox AI settings") front-loaded. It is efficient, but its brevity is partly under-specification rather than pure economy.

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 4-parameter tool with zero schema description coverage, no output schema, and conditional behavior tied to business AI settings, one sentence is not enough. The definition leaves the two required parameters and the interaction between 'instruction' and 'style' entirely undocumented.

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

Parameters1/5

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

Schema description coverage is 0% across 4 parameters and the description mentions none of them. It never explains what 'id' identifies, what the required 'text' is relative to 'instruction', or what the style enum values imply, so the agent gets no meaning beyond raw JSON Schema constraints.

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?

Names a concrete verb+resource ("Rewrite draft reply text") and a specific deliverable state ("for owner review"), which distinguishes it from sibling draft_inbox_reply that presumably creates drafts. It does not explicitly say how it differs from prepare_inbox_auto_draft, so differentiation is partial rather than complete.

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

Usage Guidelines2/5

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

The phrase "for owner review" implies a human-in-the-loop workflow and hints that output is a suggestion, not a committed draft, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. draft_inbox_reply, prepare_inbox_auto_draft). The agent must infer the routing decision from sibling names alone.

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