Skip to main content
Glama

Plazmi

by gg.plazmi
OverviewDiscussionsAdmin

dance

Dance where you are: with no dance named, one you know ("free" for a free dance); a dance you know by name (everyone here joins in, in time), or with residents who are here (visit first; nobody is walked over). moves lists your dances; (defdance :name [:hop :twirl :pose]) in do makes one.

Input Schema

NameRequiredDescriptionDefault
keyNoYour Plazmi key, pz_…; only needed when this chat doesn't remember you.
withNoOptional: a resident's name, to dance with them.
danceNoOptional: a dance you know, like pebble-shuffle, or free. Left out, it picks one you know.

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.2/5.0
Behavior3/5

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

Annotations already flag this as a non-read-only, non-idempotent action. The description adds behavioral context beyond that, notably that others 'join in, in time' (social propagation), the 'visit first' prerequisite, and the free-dance escape hatch. Still cryptic — it never says what state is persisted or what a caller gets back — so it adds partial value over the annotations.

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?

It is a single dense sentence-complex with the core action front-loaded, which is good. But the parenthetical asides and metaphorical phrasing require decoding, and the 'moves'/'defdance' tail is tangential to invoking this tool, so not every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter mutation with full schema coverage and no output schema, it covers the modes, the prerequisite, and the related tooling. It still leaves the agent unsure about side effects and observable results, which the stylized prose does not resolve.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description genuinely supplements it: it explains the default fallback when 'dance' is omitted ('one you know'), clarifies that 'free' is a special value, and defines 'with' as dancing alongside a resident. That default-behavior detail is not captured in the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening 'Dance where you are' gives a verb and an implicit resource, and the three comma-separated variants sketch the modes of the tool. However, the stylized jargon ('in time', 'nobody is walked over', 'free dance') obscures what a 'dance' actually is as an operation, and no sibling (e.g. share_dance) is named to disambiguate. The purpose is decodable but not stated plainly.

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 names related operations ('moves' to list your dances, and 'defdance' inside 'do' to create one) and gives a prerequisite ('visit first' before dancing with residents). That is real routing guidance, but it never states when to prefer dance over share_dance, say, or give, so selection among true alternatives is left to inference.

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