Skip to main content
Glama

ELI5 Park adventures

Read an ELI5 Park adventure

read_adventure
Read-only

Reads one adventure in full, as plain text, by its id (e.g. ai/ai). Use the id from search_adventures or list_adventures.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe adventure id, e.g. ai/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 the description's job is smaller; it still adds real value by disclosing the return shape ("as plain text") and that the full record is returned untruncated. It does not say what happens for an unknown id, which is the only remaining behavioral gap.

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?

Two short sentences, zero filler, with the core action and return format front-loaded and the id-provenance hint following. Every clause carries information.

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 one-parameter read tool with full schema coverage and read-only annotations, the description covers purpose, input source, and return format. Only the handling of a nonexistent id is unaddressed, which is a minor omission rather than a blocking gap.

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?

The single parameter is fully documented in the schema, including the "ai/ai" example that the description repeats. The one addition beyond the schema is provenance of the value (from search_adventures or list_adventures), which is useful but marginal at 100% schema coverage, so baseline 3 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?

States a specific verb and resource ("Reads one adventure in full") plus the retrieval key, which cleanly separates it from the list/search siblings. It does not explicitly name what it is not, but the phrase "one adventure" plus a single-id input makes the distinction obvious.

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?

"Use the id from search_adventures or list_adventures" gives the agent an explicit prerequisite and names both alternatives that produce the required input. There is no explicit when-not guidance (e.g. bulk retrieval), but the context is clear enough to route correctly.

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