Skip to main content
Glama

save_inbox_saved_reply

Idempotent

Create or update a reusable Inbox reply. Reuse the same reply ID when retrying.

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>",
      "title": "<title>",
      "body": "<body>"
    },
    "name": "save_inbox_saved_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyYes
titleYes

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=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description reinforces idempotency with a concrete retry instruction, which is useful, but it omits what an update overwrites and whether existing fields are replaced or merged.

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?

Two short sentences, front-loaded with the core action and no filler verbiage. The second sentence is terse to the point of ambiguity about what a 'retry' means, but nothing is wasted.

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 3-parameter mutation tool with 0% schema description coverage and no output schema, the description is thin. An agent still cannot tell what title and body mean, whether supplying an existing id merges or replaces content, or what is returned on success.

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 must compensate and largely doesn't. It alludes to 'reply ID' (the id parameter) but says nothing about title or body semantics, and does not mention the 80/5000 character limits or validation constraints that the schema encodes.

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 uses a specific verb pair and resource: 'Create or update a reusable Inbox reply.' That distinguishes it from the delete_/list_ siblings by name convention, though it never explicitly states it is the write counterpart to list_inbox_saved_replies.

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 only guidance is 'Reuse the same reply ID when retrying,' which is retry behavior, not when-to-use guidance. It does not say when to create versus update, nor when to use this instead of draft_inbox_reply or rewrite_inbox_reply.

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