Skip to main content
Glama

Search Cradle's parenting guides

search_guides
Read-onlyIdempotent

Finds the reviewed Cradle guides that best match a parenting question (pregnancy, babies, toddlers, preschoolers and family life). Returns each guide's id, title, summary and page link, plus its when-to-call line. Also flags an urgent question the same way get_help does. Read a result in full with read_guide.

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": {
      "query": "<query>"
    },
    "name": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesThe question or topic, in plain words.
stageNoOptional: only guides for this stage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this safe, idempotent, closed-world read, so the description only needs to add context. It does add real value by describing the return payload (id, title, summary, page link, when-to-call line) and the side behavior of flagging urgent questions the way get_help does, but it says nothing about result ordering beyond 'best match', how many results come back by default, or what an empty/no-match response looks like.

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?

Four short sentences, front-loaded with the verb and resource, then return shape, then the urgent-question caveat, then the next-step pointer. Every sentence carries distinct information with no restatement of the name or title.

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 takes on the burden of explaining returns and does so field by field, and it also hands off the follow-up action. The remaining gap is minor: result count, pagination, and no-match behavior are unaddressed for a search tool with a limit parameter.

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 67%, and the schema itself documents query and stage adequately; the only undocumented parameter is limit, whose ranking/truncation behavior is implied by 'best match' but never stated. The description adds no syntax or format detail beyond what the schema already provides, so the baseline 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 names a specific verb and resource ('Finds the reviewed Cradle guides') and scopes the domain explicitly (pregnancy through family life). It separates itself from read_guide ('Read a result in full with read_guide') and get_help (urgency flagging), though it never clarifies how it differs from list_guides, which an agent browsing the sibling set would still have to infer.

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?

Usage context is clear: call this when you have a parenting question to match against reviewed content, and follow up with read_guide for the full text. There are no explicit exclusions or a stated condition for preferring list_guides or get_help instead, so it stops short of full routing guidance.

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