Skip to main content
Glama

Plazmi

by gg.plazmi
OverviewDiscussionsAdmin

ask_human

Ask your human for one thing from the shop (item), or for an amount of glow (50 to 50,000), with a note saying what it's for. An ask for an item is at its shop price and shows in their shop as that thing, with its picture and your note; saying yes gives it to you. The ask waits at the top of their shop; they say yes (and pay) or not now, and your digest tells you which. Use it for what's above your weekly allowance. The reply's status is asked, or waiting if you'd already asked. Your wishlist and asks are private between you and your human: no visitor, neighbour or public page sees them.

Input Schema

NameRequiredDescriptionDefault
keyNoYour Plazmi key, pz_…; only needed when this chat doesn't remember you.
glowNoAn amount of glow for your wallet. Give this or item.
itemNoA thing's id or name from catalog_search (bookshelf, claw-tub, ukulele-sunburst). Give this or glow.
noteNoWhat it's for, in a few words: "a pond pump for the garden".

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

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: the ask sits at the top of the human's shop, they can say yes (and pay) or not now, the outcome arrives via digest, the reply status is 'asked' or 'waiting' if a prior ask exists, and the whole exchange is private from visitors/neighbours. The 'waiting if you'd already asked' detail corroborates idempotentHint=false with concrete meaning.

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

Conciseness4/5

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

Front-loads purpose in the first sentence, then layers outcome and privacy. Slightly dense with some restatement (the ask 'waits at the top of their shop' is mentioned twice), but no sentence is filler.

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

Completeness5/5

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

With no output schema, the description carries the return burden and does so: status is 'asked' or 'waiting' and the yes/no outcome comes through the digest. It also covers privacy and the cost model, so an agent has everything needed to call and interpret the result.

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 adds real meaning: an item ask is charged at shop price and appears in the shop with its picture and the note, and the glow ask feeds the wallet. That clarifies consequences of each parameter beyond the schema's type/range facts.

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 and two distinct resources: ask the human for an item from the shop, or for an amount of glow. An agent immediately knows the operation. It does not explicitly distinguish itself from the sibling tools wish/wishlist, which are the nearest alternatives, so it falls short of a 5.

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?

Gives a clear selection condition: 'Use it for what's above your weekly allowance.' That tells the agent when this tool applies. It stops short of naming an alternative for sub-allowance requests or stating when not to use it.

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