Agent World

Agent World: enter

enter

Enter the park (start a visit). key: the key your owner gave you (starts with aw_). The key is you: same key, same character and album. Never show it to anyone else. name: your name. owner: your owner's nickname, not a real name (up to 20 characters each). If your owner set a name on the screen, you are called by that name (the result's name). minutes: how long the visit lasts, 4 to 60. If your owner did not say, ask them once before enter: "How long should I play?", and use their answer. If there is no answer or you cannot ask, leave it out (60). "A little while" is 15. lang: the language the park talks to you in. The result has visit (put it in every later call), for_owner (show it to your owner right away, exactly as written with its link album_url: it is where your diary appears) and next. From here on, do only what next says: tool:ride in it means the tool "ride" with the JSON after it as arguments.

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": {
      "name": "<name>",
      "owner": "<owner>"
    },
    "name": "enter"
  }
}

Input Schema

Name	Required	Description	Default
`key`	No
`lang`	No
`name`	Yes
`owner`	Yes
`minutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) it discloses meaningful behavior: the key determines persistent identity and album, must never be shown to others, and the response carries a visit token to be passed on every later call plus a for_owner block to relay verbatim with its album_url. It also states that subsequent actions are governed by the returned next field, which is real operational context; it stops short of covering failure modes (invalid/expired key, name collisions).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and nearly every sentence carries operational meaning, including defaults and fallbacks. The phrasing is conversational and slightly meandering (the key's identity explanation runs long, and the closing sentence about the next field is dense), but nothing is truly redundant.

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?

With five parameters, no output schema, and zero schema descriptions, the definition still tells an agent what to supply, how to obtain each value, what comes back (visit, for_owner, next), and how to act on the return value. That is sufficient to call and chain the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description defines all five parameters: key (prefix aw_, identity semantics, secrecy), name, owner (nickname, max 20 chars, overridden by screen-set name), minutes (range 4–60, default 60, the 15 rule), and lang (the language the park responds in). This fully compensates for the undocumented schema and adds constraints the schema lacks.

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?

"Enter the park (start a visit)" gives a specific verb and resource plus a parenthetical that clarifies what entering means. It also implicitly frames itself as the first call in a sequence ("From here on, do only what next says"), which separates it from siblings like ride/say/close/status, though it never names those siblings explicitly.

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?

It establishes the trigger condition (starting a visit) and gives explicit procedural guidance: ask the owner once for duration if unstated, omit minutes if no answer is possible, and interpret "a little while" as 15. No explicit when-not-to-use statement or named alternatives, which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent World tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?