Skip to main content
Glama

get_inbox_auto_draft

Read-onlyIdempotent

Read the saved automatic reply draft for a customer message in the approved business. Returns null when no draft exists.

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

Input Schema

NameRequiredDescriptionDefault
idYes
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world scope, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it returns null when no draft exists, telling the agent a missing draft is a normal outcome rather than an error. It still says nothing about failure modes or response shape, so a 3 is appropriate.

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 lean sentences with the core action front-loaded and zero padding. Sizing fits a simple read tool; the only missing element is a clarifying clause identifying the two parameters.

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

Completeness3/5

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

For a two-parameter read-only fetch with full annotation coverage and no output schema, the description covers the essential scope and the null case. It falls short by leaving both required parameters unexplained at 0% schema description coverage, which is the main thing an agent could get wrong when invoking it.

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 description coverage is 0% and neither of the two required parameters (id, messageId) is documented, so the description must carry the meaning and only partially does: "customer message" maps loosely to messageId and "the approved business" hints that id is a business identifier. It never states this mapping explicitly or adds format constraints, leaving the agent to infer which value goes where.

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?

States a specific verb plus resource ("Read the saved automatic reply draft") and scopes it to "a customer message in the approved business," which lets an agent separate it from prepare_inbox_auto_draft and list_inbox_auto_drafts. It does not explicitly name a sibling, which keeps it short of 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?

No when-to-use or when-not-to-use guidance is given; the agent must infer that this fetches a single existing draft rather than preparing or listing drafts. The phrase "in the approved business" implies a per-message lookup context but names no alternative, explicit condition, or prerequisite.

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