Skip to main content
Glama

ELI5 Park adventures

List ELI5 Park adventures

list_adventures
Read-only

Lists every adventure (id, title, link), grouped by section: Artificial Intelligence, Technology, Money, Careers, Body & Mind, Medical, Cooking, Nepal and more. Kid adventures by default; grown-up guides need audience=grownups.

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

Input Schema

NameRequiredDescriptionDefault
audienceNoKid adventures by default. Use grownups for the grown-up sections; all for both.kids
categoryNoOptional: one section only, e.g. 'Cooking' or 'cooking'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish read-only and closed-world behavior. The description adds useful context about grouping by section, returned fields, and the default audience, but it does not discuss ordering, pagination, or other runtime behavior.

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?

The description is two compact sentences and is front-loaded with the core listing behavior. Every sentence contributes useful information with no filler.

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 two-parameter list tool without an output schema, the description is largely complete: it names returned fields, explains grouping, and clarifies the audience default. The main remaining gap is the absence of explicit guidance on choosing this tool over its search/read siblings.

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 the schema already carries the parameter documentation burden. The description repeats the default audience and lists possible sections, which marginally helps category semantics, but adds little beyond the existing 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?

The description clearly states a specific verb and resource: it lists adventures and notes returned fields (id, title, link) grouped by section. It does not explicitly contrast itself with search_adventures or read_adventure, so sibling differentiation is missing.

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?

It gives useful audience guidance (kids by default, grownups via audience=grownups) and implies this is a browse-all tool. However, it does not state when to use this instead of search_adventures or read_adventure, nor does it set exclusions.

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