Skip to main content
Glama

prepare_inbox_auto_draft

Idempotent

Prepare or retrieve the shared Inbox reply draft for a customer message when automatic drafts are enabled in the approved business.

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": "prepare_inbox_auto_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context the annotations do not: the draft is 'shared', it is tied to a customer message, and it only applies when automatic drafts are enabled and the business is approved. It does not say what is returned or what happens if the precondition fails, so it goes beyond annotations but not far.

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 tightly written sentence with the action and the eligibility condition front-loaded and no filler. Its brevity is close to excessive given the unexplained parameters, but nothing in it 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?

No output schema exists and both required parameters are undocumented, so the description carries the full explanatory load for a non-read-only, draft-creating tool. It covers purpose and eligibility but omits return behavior, the identity of the two IDs, and failure semantics when automatic drafts are disabled.

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 carry the parameter burden and does not. It never explains what 'id' identifies (inbox, business, or customer) or what 'messageId' refers to, leaving both required params opaque beyond their names.

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 pair ('Prepare or retrieve') and a specific resource ('the shared Inbox reply draft for a customer message'), with a gating condition attached. It is mostly distinguishable from siblings, though the 'retrieve' half overlaps with get_inbox_auto_draft and the description never resolves that overlap.

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

Usage Guidelines3/5

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

Provides a real precondition ('when automatic drafts are enabled in the approved business'), which tells the agent roughly when this applies. However, it names no alternative for the retrieval case (get_inbox_auto_draft) and gives no guidance on what to do when automatic drafts are not enabled.

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