Skip to main content
Glama

ELI5 Park adventures

Search ELI5 Park adventures

search_adventures
Read-only

Finds the ELI5 Park adventures that best match a question or topic. Returns each adventure's id, title, section and page link. Kid adventures by default; grown-up guides need audience=grownups. Read a result in full with read_adventure.

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_adventures"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoThe question or topic, in plain words.
audienceNoKid adventures by default. Use grownups for NCLEX, parenting, pregnancy, money planning and coding interviews; all for both.kids
categoryNoOptional: only adventures in this section, e.g. 'Artificial Intelligence' or 'ai'.

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 readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value by disclosing the default audience behavior and the exact result fields (id, title, section, page link), which matters since no output schema exists.

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 purpose, then return shape, then the two routing facts. Every sentence carries information an agent needs.

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 four-parameter read-only search with no output schema, the description covers purpose, return fields, audience default, and the follow-up tool. Only pagination/limit behavior and the category filter's semantics are left entirely to the schema.

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 75%, with query and audience already documented in the schema. The description restates the audience default but adds no meaning for limit or category, so it stays at the baseline for a well-documented schema.

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?

States a specific verb ("Finds") and resource ("ELI5 Park adventures") scoped to matching a question or topic, which implicitly separates it from list_adventures. It explicitly routes the agent to read_adventure for full content, though it does not directly contrast itself with list_adventures.

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?

Gives clear conditional guidance: kid adventures by default, grown-up guides require audience=grownups, and full content requires read_adventure. It does not state when to prefer list_adventures over this search, which keeps it short of a 5.

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