Skip to main content
Glama

Search Guides Tool

search_guides
Read-onlyIdempotent

Search Kidincare's published parenting and childcare guides, such as how to choose a daycare or what to ask on a tour. Returns each guide's title, summary and link. Leave query empty for the newest guides.

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": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many guides to return.
queryNoTopic to search for, e.g. "infant care" or "daycare tour".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description correctly avoids restating safety and instead adds value: the exact fields returned and the empty-query fallback to newest guides. It stops short of describing ordering beyond that default or any result-count behavior, which is a minor gap for a search tool.

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?

Three short sentences, front-loaded with the what, then the return shape, then the empty-query rule. No filler, no repetition of schema constraints, and every sentence carries distinct information.

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?

For a two-parameter read-only search with no output schema, the description covers purpose, return fields, and the zero-query case, while the schema fully documents both parameters and annotations cover the safety profile. Nothing an agent needs in order to invoke it correctly is missing.

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 description coverage is 100%, so both limit and query are already documented with defaults and bounds, making 3 the baseline. The description adds only one incremental semantic — empty query means newest guides — which is genuinely useful but doesn't extend the meaning of limit or clarify query matching behavior (e.g., keyword vs. fuzzy).

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 ("Search Kidincare's published parenting and childcare guides") and adds concrete topical examples ("how to choose a daycare or what to ask on a tour") plus the return shape (title, summary, link). The resource domain alone separates it from siblings like search_centers and get_center, so an agent can route correctly.

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?

Offers one concrete usage rule — "Leave query empty for the newest guides" — which tells the agent how to browse rather than search. However, it never states when to prefer this over the center-oriented siblings (search_centers, list_cities) for overlapping questions like choosing a daycare. Usage is implied rather than fully scoped.

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