Skip to main content
Glama

List guides

list_guides
Read-only

Lists teaching guide summaries by most recent update, with optional draft or finished filters, and prompts users to create a missing guide via create_guide.

Instructions

List guide summaries sorted by most recently updated, optionally filtered to drafts or finished guides. Always include the invitation to ask whether the user wants to create a missing guide with create_guide.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOptional status filter; omit to list all guides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavior beyond that: results are summaries (not full content), they come back most-recently-updated first, and the agent is required to offer create_guide for a missing guide. It omits any statement about result count or pagination, which is the main remaining gap for a list tool.

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 ordering and filter before the follow-up obligation; nothing is padded. The second sentence is phrased as an imperative instruction rather than a description, which slightly mixes registers, but it is short and purposeful.

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?

For a zero-required-parameter read tool with annotations covering the safety profile and no output schema, the definition covers purpose, ordering, filtering, and the required follow-up action. Only pagination/result-size behavior is unstated, which is a minor omission at this complexity.

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% and the single enum parameter already documents itself ("Optional status filter; omit to list all guides"). The description only restates the same two allowed values, adding no format or default detail beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ("List guide summaries") plus the ordering ("sorted by most recently updated") and the optional filter ("drafts or finished guides"). That is enough to distinguish it from every listed sibling, which are all create/edit/section-level operations rather than listing operations, though it does not explicitly say so.

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?

It gives clear context for the status filter (omit to list all, filter for drafts or finished) and routes the agent to a named alternative, create_guide, when a requested guide is missing. It stops short of stating when not to use this tool, e.g. when the user wants full guide content rather than summaries.

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