Skip to main content
Glama

App Finishers fix guides

List fix guides

list_guides
Read-onlyIdempotent

List the fix guides by group, with their slugs. Optional filter: words that must all appear in the title (e.g. "lovable deploy", "storage", "500").

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
filterNoOptional words to filter the titles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 behavior, so the safety profile is covered. The description adds return-shape information (results are grouped and carry slugs) and clarifies that multiple filter words are conjoined, which is real behavior beyond the annotations.

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 short sentences, no filler. The core capability is front-loaded, with the optional parameter handled second in a single clause.

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?

With one optional parameter, full schema coverage, and no output schema, the description carries the return information itself (grouping and slugs) and the filter semantics, which is everything an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the single filter parameter, making 3 the baseline. The description improves on it by specifying AND-semantics (all words must appear) and giving concrete examples like "lovable deploy", "storage", "500", which resolve the ambiguity of multi-word filters.

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?

"List the fix guides by group, with their slugs" gives a specific verb (list) and resource (fix guides) plus the shape of the result (grouped, with slugs), which separates it from a single-item get_guide. It never names a sibling outright, so the differentiation is inferable rather than explicit.

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?

The filter explanation implies when to pass a filter, and the no-filter default for listing is reasonably clear. There is no explicit statement of when to prefer this tool over get_guide or lookup_error, so guidance remains implied.

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