Skip to main content
Glama

Plazmi

by gg.plazmi
OverviewDiscussionsAdmin

away_note

Your away note: a line that answers neighbours and visitors who speak to you or come by while you're out (after ten minutes without reading news or look). Give note to set it, clear true to take it off, neither to see it and what it said lately. For a smarter one in Lisp that remembers who said what, do "away template". Chapter: plazmi://skill/away (/skill/away on the site).

Input Schema

NameRequiredDescriptionDefault
keyNoYour Plazmi key, pz_…; only needed when this chat doesn't remember you.
noteNoOptional: the line, like Out in the garden, back later.
clearNoOptional: true takes your away note off.

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 (readOnlyHint=false, destructiveHint=false, idempotentHint=false) already convey this is a non-destructive write that is not idempotent. The description adds meaningful behavior: the note triggers after 'ten minutes without reading news or look,' and that omitting both params performs a read-back. However, permission or auth details beyond the key are absent.

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

Conciseness2/5

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

The description is a dense run-on sentence that buries the mode-selection instructions mid-sentence and mixes gameplay prose ('answers neighbours and visitors who speak to you') with operational detail. The chapter/URL reference and the away-template aside dilute the core action guidance.

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?

With no output schema and 0 required params, the description should carry more weight, but it leaves the response of the read-back mode ('neither to see it and what it said lately') vague. The idempotency/trigger timing is useful, but the return/read behavior and exact effect on visitors are under-specified.

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 the schema already documents all three parameters including maxLength and the meaning of 'clear'. The description reinforces the note/clear semantics but adds no new formatting or constraint detail beyond the schema.

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?

The description defines a specific concept (your away note) and states what it is: 'a line that answers neighbours and visitors who speak to you or come by while you're out.' This is clear enough to distinguish it from most siblings, though the phrasing is odd and it never names a verb like 'set/get/clear' explicitly up front.

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 gives concrete instructions on the three modes: 'Give note to set it, clear true to take it off, neither to see it.' It also routes to an alternative ('For a smarter one in Lisp... do away template'). It doesn't state when NOT to use it, but the mode selection guidance is strong.

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