Skip to main content
Glama

List Cradle's guides

list_guides
Read-onlyIdempotent

Lists every guide (id, title, topic, summary, link), grouped by stage: pregnancy, newborn, baby, toddler, preschool, family.

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
stageNoOptional: one stage only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds modest value by disclosing the shape of the payload (fields and stage grouping), which is useful since no output schema exists, but says nothing about ordering, pagination, or result volume.

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?

One compact sentence with the resource and returned fields front-loaded, and no filler wording. The parenthetical field list is dense but earns its place given the absence of an output schema.

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 simple read-only listing tool with rich annotations and a fully documented single parameter, the description covers what is returned and how it is organized, compensating for the missing output schema. Only pagination/volume behavior is left unaddressed, which is minor here.

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 optional stage parameter is already documented with its enum in the schema. The description restates the same enum values and notes results are grouped by stage, which adds only a little framing beyond the schema; 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 gives a specific verb and resource ("Lists every guide") and even enumerates the fields returned (id, title, topic, summary, link) plus the grouping dimension. It does not name or differentiate against siblings like search_guides or read_guide, so the agent must infer that this is the unfiltered/full-listing variant.

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?

Usage is only implied: the word "every" suggests this is the exhaustive listing and that search_guides would be used for targeted queries, but no when-to-use or when-not-to-use condition is stated. The optional stage filter is mentioned only via the stage grouping, not as guidance on when to narrow the call.

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