Skip to main content
Glama

Read a Cradle guide

read_guide
Read-onlyIdempotent

Returns one guide in full as markdown: its sections, when to call, any data tables, its sources and page link.

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

Input Schema

NameRequiredDescriptionDefault
idYesA guide id from search_guides or list_guides, e.g. colic-and-crying.

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 establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context, and it does: it discloses the return format (markdown) and the payload shape (sections, call conditions, data tables, sources, page link). It does not mention error behavior for an invalid id or any size/length limits, which keeps it just short of a 5.

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?

One front-loaded sentence with zero filler: the verb and return format come first, followed by a compact list of what the payload contains. Nothing is repeated from the schema or annotations.

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 must describe the return value, and it does so concretely enough for an agent to know what it will get back. For a one-parameter read tool with full annotation coverage, the only remaining gap is failure behavior on a bad id, which is minor.

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%: the id parameter already documents its type, an example value, and its provenance from search_guides or list_guides. The description adds nothing about the identifier beyond what the schema states, so the baseline of 3 applies.

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?

"Returns one guide in full as markdown" names a specific verb and resource, and the enumeration of contents (sections, when to call, data tables, sources, page link) makes it unmistakable against list_guides and search_guides, which return abbreviated results.

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 phrase "in full" implies this is the tool to use when summary-level results are insufficient, but the description never states that explicitly, names no alternative, and gives no exclusion. The retrieval workflow is only implied, and mainly by the id parameter's schema text pointing to search_guides or list_guides.

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