Skip to main content
Glama

agents_get_draft

Read-onlyIdempotent

Get one agent draft with its FULL text, whatever its status (pending, approved, rejected, expired...).

agents.list_drafts cuts the reply and the trigger message short; this returns both in full, so a long draft can be read or edited. Returns draft_id, thread_id, status, response_text, trigger_text, created_at.

Use this when user asks:

  • 'Show me the whole draft'

  • 'What exactly does draft 123 say?'

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": {
      "draft_id": "<draft_id>"
    },
    "name": "agents_get_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYesID of the draft (from agents.list_drafts)
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description adds the non-obvious behavioral fact that status is irrelevant (pending, approved, rejected, expired all work) and that the full untruncated text is returned. It stops short of noting what happens for a missing or unknown draft_id.

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?

Front-loaded with the full-text guarantee, then a comparison to the sibling, then a compact returned-field list and example queries. Slightly repetitive between the opening clause and the bullet list, but no sentence is filler.

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

Completeness5/5

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

For a two-parameter read tool with no output schema, the description compensates by enumerating the returned fields (draft_id, thread_id, status, response_text, trigger_text, created_at). Combined with annotations, an agent has everything needed to call it and interpret the response.

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 100%, so both parameters are already documented, and the description adds essentially no new meaning beyond the schema's own gloss for draft_id ('from agents.list_drafts'). The in_workspace override is not mentioned at all in the description, leaving that parameter entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get one agent draft') plus an explicit scope ('with its FULL text, whatever its status'), and names the sibling it is not (agents.list_drafts) and how the two differ. An agent can pick it apart from the list tool without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative (agents.list_drafts) and the exact reason to switch (it 'cuts the reply and the trigger message short'), then anchors selection with two literal user phrasings. Nothing about when to reach for this tool is left to inference.

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.