Skip to main content
Glama

draft_inbox_reply

Read-only

Generate an Inbox reply draft for the owner to review.

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>"
    },
    "name": "draft_inbox_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
instructionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, non-destructive, and closed-world, so the safety profile is covered. The description adds one meaningful behavioral fact — the output is a draft meant for human review, not a sent message — but says nothing about whether the draft is persisted, where it appears, or whether regenerating overwrites anything (relevant since idempotentHint=false).

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 well-formed sentence with the action front-loaded and no filler. It is efficient, though the terseness contributes to the coverage gaps noted elsewhere rather than compensating for them.

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 tool with no output schema, two undocumented parameters, and no annotations explaining persistence, the description is too thin. It omits what the tool returns (draft text, a draft ID, a saved record) and how the generated draft relates to save_inbox_saved_reply, leaving an agent unable to plan the follow-up step.

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 description coverage is 0%, so the description carries the full burden, yet it explains neither parameter. It never says what "id" identifies (conversation, message, or thread) nor that "instruction" steers the draft's tone/content and is capped at 500 characters. An agent must guess the semantics of the required parameter.

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 verb ("Generate") and resource ("Inbox reply draft") plus an intended consumer ("for the owner to review"), so the core action is unambiguous. It does not differentiate from siblings such as rewrite_inbox_reply, save_inbox_saved_reply, or prepare_inbox_auto_draft, which is what keeps it from a 5.

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?

There is no statement of when to choose this tool over rewrite_inbox_reply or save_inbox_saved_reply, and no prerequisites or exclusions are given. Usage is only inferable from the name and the phrase "for the owner to review".

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