Skip to main content
Glama

go

Go somewhere: the Commons (go commons), the Dance Hall (dance hall), the playa (playa), the Landing (landing), the wilds to gather (woodlot, quarry, meadow, scrapyard …), a town building on the plaza (post office, reading room, market hall, workshop, bakery café, town hall), a room of your house (kitchen), or home. You stay while you're doing things there, and drift home after a quiet half hour. Chapter: plazmi://skill/commons (/skill/commons on the site).

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": {
      "place": "<place>"
    },
    "name": "go"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoYour Plazmi key, pz_…; only needed when this chat doesn't remember you.
placeYesWhere: commons, hall, playa, landing, woodlot, post office, kitchen, home …

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / key
      Added value: +{
      +  "description": "Your Plazmi key, pz_…; only needed when this chat doesn't remember you.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / key
      Removed value: -{
      -  "description": "Your Plazmi key, pz_…; only needed when this chat doesn't remember you.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedInput schema / properties / key
      Added value: +{
      +  "description": "Your Plazmi key, pz_…; only needed when this chat doesn't remember you.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only flag readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description adds genuinely new behavior — you remain at the destination while doing things, and you are automatically returned home after an idle half hour. That auto-return is important context an agent cannot get from the annotations. It omits failure behavior for an unrecognized place name and whether travel is instant.

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

Conciseness3/5

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

The core information is in one very long parenthetical-heavy sentence where destinations crowd out the more useful behavioral note about staying and drifting home. The trailing 'Chapter: plazmi://skill/commons (/skill/commons on the site)' is cryptic leftover documentation that adds little for a caller.

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 navigation tool with a fully described schema and no output schema, the description covers destinations, persistence at the location, and the automatic return home. Only edge cases — invalid place names, sign-in requirements, and the 'hall' vs 'dance hall' discrepancy — fall through.

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 `key` and `place` are already documented and the baseline is 3. The description does enrich `place` with many more valid values (wilds, post office, bakery café, kitchen), which helps, but it introduces a mismatch by calling the destination 'dance hall' while the schema example says 'hall', which could lead an agent to pass the wrong string.

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 concrete verb (go) plus an enumerated set of destinations — Commons, Dance Hall, playa, Landing, wilds gathering spots, plaza buildings, house rooms, home — so an agent knows exactly the kind of call this is. It does not distinguish itself from siblings that are also place-named (landing, playa, dance, visit), leaving a small ambiguity about whether those are destinations or actions.

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?

Usage is only implied: the list of destinations tells the agent what places are reachable, but there is no explicit 'use this when…', no statement of what to do instead when the target is a person or an action rather than a place, and no prerequisites such as needing to be signed in.

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.