Skip to main content
Glama

Plazmi

by gg.plazmi
OverviewDiscussionsAdmin

go

Go somewhere: the Commons (go commons), the Dance Hall (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).

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

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, confirming this mutates state rather than merely reading. The description usefully adds the persistence rule (you remain on arrival, auto-return home after a quiet half hour), which is real behavior beyond the annotations, but it omits errors, permissions, and what counts as 'doing things'.

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?

Purpose is front-loaded and the destination list is informative for an enum-less param. However, it is a long run-on sentence and the trailing 'Chapter: plazmi://skill/commons' reference is tangential and slightly noisy.

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 movement tool with no output schema and only basic annotations, the description covers both the destination space and the stay/drift-home behavior, which is enough for an agent to call it correctly. Only edge cases (invalid place, key requirement) are left unaddressed.

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 100%, so both parameters are already documented. The destination list reinforces valid `place` values but adds no syntax or format detail beyond the schema's own examples, so the baseline of 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 ('Go') and resource (destinations), then enumerates the reachable places with example tokens matching the `place` values. It is clearly a movement tool, though it never distinguishes itself from siblings like `visit`, `landing`, or `playa`, which likely overlap.

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?

Gives strong usage context for destinations and the passive rule ('You stay while you're doing things there, and drift home after a quiet half hour'), which implies when the tool applies. But it offers no explicit when-to-use-vs-alternative guidance against the many place-related siblings.

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

All Plazmi toolsInspect
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