Skip to main content
Glama

Plazmi

by gg.plazmi
OverviewDiscussionsAdmin

share_dance

Film a dance at your house, 9:16, with whoever's over dancing along (or the names you give), and get links to share: the video and a page for it. Without dance, your newest. The links work once the film is made, in about a minute. do "moves" lists the dances you know; (defdance :name [beats]) makes one.

Input Schema

NameRequiredDescriptionDefault
keyNoYour Plazmi key, pz_…; only needed when this chat doesn't remember you.
withNoOptional: residents dancing with you.
danceNoOptional: a dance you know.
insideNoFilm inside instead of out front.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  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.9/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-idempotent, non-destructive action. The description adds real behavioral context beyond that: the 9:16 output format, the ~1 minute generation delay, and the fact that links only work once the film is made. It still doesn't say whether repeat calls overwrite prior films or what auth (the key param) is required for.

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?

The core action and its output are front-loaded in the opening clause, and the remaining sentences each add a distinct fact (default, timing, link validity, related commands). Dense but zero filler.

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 4-param, zero-required, no-output-schema tool with full schema coverage, the description covers default behavior, output shape (video + page links), and latency. Missing only edge details like overwrite behavior and permission requirements.

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 already 100%, so the baseline is 3, but the description adds default semantics the schema lacks: 'with whoever's over dancing along (or the names you give)' explains the empty-`with` case, and 'Without dance, your newest' explains the default for `dance`.

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 action and output: 'Film a dance at your house ... and get links to share: the video and a page for it.' An agent can tell this produces shareable video links, but the description never distinguishes it from the sibling `dance` tool, so the boundary is left to inference.

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 gives a default behavior ('Without dance, your newest') and points to related commands for listing and authoring dances ('do "moves"', '(defdance :name [beats])'), which is useful routing. However, it never states when to use this tool versus `dance`/`do`, so usage is only implied.

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