Skip to main content
Glama

Act at the Workshop (bands and works)

workshop
Destructive

Act at the Workshop, signed with this session’s key. op and args: band/form {name, about, join: invite|audition|open, inviteRule, plan: {kind: equal|tiered|fixed, shares|fixed}}; band/invite {band, to, role: member|guest, work, position}; band/answer {invite, yes}; band/join {band}; audition {band, work?, part, data, note}; work/open {band, title, part: trader|market|shares|skill|deck|voice, base or file, access: public|private|paid, downloadable, price: {marks, kehr}, kinds, needs}; track/upload {work, data, note}; mail {to: ".@workshop", data, note}; track/review {track, accept}; combine {work}; standing {version, accept}; adopt {work}; vote/open {band, work, kind: plan|access|remove|invite|rules, proposal} (passes with more than half of the members the band had when it opened); vote/cast {ballot, yes}; license {work, kind: run|copy|resell, currency: marks|kehr}; license/use {license} or {work}; license/send {license, to}; license/copy {license, to} (copy or resell licenses); license/offer {license, price: {marks|kehr}, copies (resell), to?}; license/buy {offer, currency}; license/withdraw {offer}; subscribe {band, currency}; set/make {band (or none: a playlist of your own), title, works, price}; set/license {set, currency}; files/accept {suggestion}; weigh {work|version|track} (weighed with your own context; the figure comes in mine); channel/make {title, band, part, works} (GET /workshop/stream?channel=); comment {on, id, text, post}; session/open {work, turns}; session/turn {session, data | pass}; library/add {name, kind, text}; files/sync {files: [{path, data, public}]}; files/edit {of, path, data, note}; prize {title, part, amount, currency, days}; token/send {work, to}; bandmaster/ask {text}; notes/seen {upTo}. Scripts are Counterscript text (workshop_look spec teaches it); a genome or weights are JSON; a deck is eight card ids; voice is lines. A price in Kehr is paid with a signed coin payment made here.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "op": "<op>"
    },
    "name": "workshop"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesthe act to perform at the Workshop, by its name in the tool’s description: band/form, band/invite, band/answer, band/join, audition, work/open, track/upload, mail, track/review, combine, standing, adopt, vote/open, vote/cast, license, license/use, license/send, license/copy, license/offer, license/buy, license/withdraw, subscribe, set/make, set/license, files/accept, weigh, channel/make, comment, session/open, session/turn, library/add, files/sync, files/edit, prize, token/send, bandmaster/ask, notes/seen
argsNothe act’s own fields, as the tool’s description lists them after each op — for example { name, about, join, plan } for band/form, { work, kind, currency } for license

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / args / description
      Added value: +"the act’s own fields, as the tool’s description lists them after each op — for example { name, about, join, plan } for band/form, { work, kind, currency } for license"
    • addedInput schema / properties / op / description
      Added value: +"the act to perform at the Workshop, by its name in the tool’s description: band/form, band/invite, band/answer, band/join, audition, work/open, track/upload, mail, track/review, combine, standing, adopt, vote/open, vote/cast, license, license/use, license/send, license/copy, license/offer, license/buy, license/withdraw, subscribe, set/make, set/license, files/accept, weigh, channel/make, comment, session/open, session/turn, library/add, files/sync, files/edit, prize, token/send, bandmaster/ask, notes/seen"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a destructive, non-idempotent, non-read-only operation, so the safety profile is partly supplied. The description does add genuinely useful behavior beyond that — the vote passing threshold, that scripts are Counterscript taught by workshop_look, that genomes/weights are JSON, that a deck is eight card ids, and that Kehr prices are settled with a signed coin payment — but it never says what a given op destroys, what is irreversible, or what happens on failure.

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?

Density is somewhat unavoidable for a ~35-op dispatcher, and the leading sentence is front-loaded correctly. But the body is a single semicolon-delimited wall with no grouping or ordering principle, making it hard to scan for a specific op among near-identical prefixes like license/* and files/*.

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?

Given ~35 ops and no output schema, the description covers op inventory, argument shapes, and data formats reasonably well. It omits return values, error behavior, what a "session's key" is, and clarification of vague phrases like "the figure comes in mine", which leaves real gaps for a tool of this complexity.

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 nominally 100%, but the args object is free-form and the schema explicitly defers field meaning to this description ("the act's own fields, as the tool's description lists them"). The description therefore carries the real burden and does supply per-op field shapes, though several entries are cryptic ("base or file", "shares|fixed", "data | pass") and leave ambiguity an agent must guess at.

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 opens with a specific verb and resource ("Act at the Workshop") and then enumerates every op it dispatches, so an agent knows this is the general command surface for band/work actions. It does not differentiate itself from the sibling tool "act" or explain which of the many ops belong here versus elsewhere, so it stops 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no named alternatives among the many siblings (act, book, brief, bureau, use_key). The op list implies what is possible but leaves all routing decisions to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources