Skip to main content
Glama

list_builder_guides

Read-onlyIdempotent

List Ballet authoring guides available to this workspace (id, name, description, keywords). Use when choosing which get_builder_guide topics to load before creating a playbook, agent, tool, or skill.

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_builder_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSubstring match across id, name, description, and keywords

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds the genuinely useful constraint that results are limited to 'this workspace' and enumerates the returned fields, but says nothing about result volume, pagination, or what an empty list means. Solid additive context, not rich behavioral disclosure.

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?

Two sentences, zero padding: the first establishes what is listed and what comes back, the second immediately routes to the next step. What the tool returns is front-loaded before the usage guidance, which is the right order for a discovery tool.

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 no-required-parameter, single-parameter list tool with no output schema, the description supplies the missing return shape (id, name, description, keywords) and the sequencing into get_builder_guide. Only minor gaps remain around result-set size and behavior when the query matches nothing.

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?

The single `query` parameter is fully documented in the schema as a substring match, so schema coverage is 100% and the baseline applies. The description's parenthetical field list (id, name, description, keywords) mirrors the schema's match targets and confirms the search surface, but adds no syntax, casing, or matching-behavior detail beyond it.

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 ('List Ballet authoring guides') plus the workspace scope and the fields returned (id, name, description, keywords). It also distinguishes itself from the retrieval sibling by framing itself as the step that picks which 'get_builder_guide topics to load', so an agent can separate list-from-get 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 Guidelines4/5

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

Gives a clear triggering context ('when choosing which get_builder_guide topics to load before creating a playbook, agent, tool, or skill') and names the follow-up tool explicitly. It stops short of stating when-not to use it (e.g., when the guide id is already known), so it is strong routing rather than complete routing.

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