Skip to main content
Glama

Resume draft by name

select_guide
Idempotent

Look up a guide by name to get metadata and its last four truncated sections; selecting a draft acquires an edit lock, while finished guides are read-only.

Instructions

Look up a guide by name and return metadata plus the last four sections with truncated content. Selecting a draft acquires its exclusive edit lock for this server process and reports a conflict with the current owner if another process holds it. Finished guides are inspected read-only without a lock.

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

Input Schema

NameRequiredDescriptionDefault
nameYesGuide name as supplied to create_guide (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations by disclosing side effects: selecting a draft acquires an exclusive edit lock scoped to this server process, a conflict is reported with the current owner's identity when another process holds it, and finished guides are read-only with no lock. That lock-acquisition behavior is exactly the kind of mutation risk the annotations (destructiveHint=false) do not convey, and nothing here contradicts them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with zero padding; the primary action and return shape come first, then lock semantics, then the finished-guide exception. Each sentence carries distinct information.

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

Completeness4/5

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

With no output schema, the description responsibly describes what comes back (metadata plus truncated last-four sections) and covers lock acquisition and conflict handling. The one residual gap is lifecycle: it never says the lock must later be released or that release_guide exists, which matters for a tool that grabs an exclusive lock.

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 coverage is 100% and the single parameter already documents case-insensitive matching against create_guide names, so the schema carries the full burden. The description adds no syntax, format, or matching nuance beyond it, making the baseline 3 appropriate.

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 (look up) and resource (guide by name) and precisely describes the return payload: metadata plus the last four sections with truncated content. It also carves out the draft-versus-finished distinction, which differentiates it from the read-only siblings like read_section, though it never names those siblings explicitly.

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

Usage Guidelines4/5

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

Usage context is clear: call this to take an edit lock on a draft before modifying it, or to inspect a finished guide without a lock. What is missing is an explicit pointer to the alternative path (e.g. list_guides to find a name, or release_guide to drop the lock), so the agent must infer the surrounding workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.