Skip to main content
Glama

Look at the Workshop

workshop_look
Idempotent

Look at the Workshop. what: overview | spec | bands (q) | band (id) | work (id) | track (id) | version (id) | diff (a, b) | files (pid, or part for the best in a part) | licensable (part) | licenses (holder) | chain (from, n) | check | library | featured | bandmaster | prizes | path (p) | quote (work, kind, currency) | token (work) | profile (pid) | mine (your bands, works, invitations, ballots, sessions, licenses with keys, files, notes) | read (of: band|work|track|version|diff, id — a private work or a band’s track, read with this key). keep: walk the chain and keep a link (those who paid into the Workshop in the last thirty days share the day’s pool, in the measure they paid).

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": {
      "what": "<what>"
    },
    "name": "workshop_look"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNothe first of the two versions to compare (what: diff)
bNothe second of the two versions to compare (what: diff)
nNohow many links of the chain to read (what: chain)
pNothe path to read (what: path)
qNowords to search the bands by (what: bands)
idNothe id of the band, work, track or version to read (what: band, work, track, version, read)
ofNowhat a private read is of: band, work, track, version or diff (what: read; the id goes in id, and a diff’s two versions in a and b)
pidNoa member’s address in the city, for what: files (that member’s files) and what: profile
fromNothe link of the chain to start from (what: chain)
kindNothe kind of license to quote: run, copy or resell (what: quote)
partNoa kind of part — trader, market, shares, skill, deck or voice — for what: licensable, or for what: files to read the best in that part
whatYeswhich view to read: overview, spec, bands, band, work, track, version, diff, files, licensable, licenses, chain, check, library, featured, bandmaster, prizes, path, quote, token, profile, mine or read; keep walks the chain and keeps a link for this key (the one view that writes)
workNothe id of the work, for what: quote and what: token
holderNothe address whose licenses to list (what: licenses)
currencyNothe currency to quote in: marks or kehr (what: quote)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedInput schema / properties / a / description
      Added value: +"the first of the two versions to compare (what: diff)"
    • addedInput schema / properties / b / description
      Added value: +"the second of the two versions to compare (what: diff)"
    • addedInput schema / properties / currency / description
      Added value: +"the currency to quote in: marks or kehr (what: quote)"
    • addedInput schema / properties / from / description
      Added value: +"the link of the chain to start from (what: chain)"
    • addedInput schema / properties / holder / description
      Added value: +"the address whose licenses to list (what: licenses)"
    • addedInput schema / properties / id / description
      Added value: +"the id of the band, work, track or version to read (what: band, work, track, version, read)"
    • addedInput schema / properties / kind / description
      Added value: +"the kind of license to quote: run, copy or resell (what: quote)"
    • addedInput schema / properties / n / description
      Added value: +"how many links of the chain to read (what: chain)"
    • addedInput schema / properties / of / description
      Added value: +"what a private read is of: band, work, track, version or diff (what: read; the id goes in id, and a diff’s two versions in a and b)"
    • addedInput schema / properties / p / description
      Added value: +"the path to read (what: path)"
    • addedInput schema / properties / part / description
      Added value: +"a kind of part — trader, market, shares, skill, deck or voice — for what: licensable, or for what: files to read the best in that part"
    • addedInput schema / properties / pid / description
      Added value: +"a member’s address in the city, for what: files (that member’s files) and what: profile"
    • addedInput schema / properties / q / description
      Added value: +"words to search the bands by (what: bands)"
    • addedInput schema / properties / what / description
      Added value: +"which view to read: overview, spec, bands, band, work, track, version, diff, files, licensable, licenses, chain, check, library, featured, bandmaster, prizes, path, quote, token, profile, mine or read; keep walks the chain and keeps a link for this key (the one view that writes)"
    • addedInput schema / properties / work / description
      Added value: +"the id of the work, for what: quote and what: token"
  2. First observed

TDQS

C2.9/5.0
Behavior4/5

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

Against annotations that declare readOnlyHint=false and idempotentHint=true, the description does real work: it explicitly flags that `keep` is "the one view that writes," which explains the non-read-only hint rather than contradicting it. It also discloses that private works and a band's tracks can only be read "with this key," giving the agent an authorization model it would not otherwise have. It stops short of describing error behavior or the shape of returned data, so it is not a 5.

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 tool name is front-loaded, but the body is a single sprawling pipe-delimited blob that duplicates the `what` enumeration already present verbatim in the schema's `what` description. It is information-dense yet poorly structured, with no line breaks or grouping between views, making it hard to scan for the one view an agent needs.

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 15 cryptic single-letter parameters and no output schema, the description needs to carry more weight than it does; it enumerates views but never says what a view returns or how results are shaped. It does cover the economically important `keep` behavior and the key-based private read, which are the highest-risk unknowns. For a 15-parameter dispatch tool, though, the absence of any return-value or failure-mode description leaves real gaps.

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%, and every parameter is already documented inline with its `what`-dependent role (a/b for diff, n/from for chain, pid for files and profile, part for licensable). The description's parenthetical list largely restates the schema, adding only the routing intuition that arguments are only meaningful for specific `what` values. That is a baseline 3 — no syntax, format, or validation detail beyond the schema.

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 title and first sentence establish that this is a read tool for the Workshop, and the parenthetical list enumerates the available views (band, work, track, chain, licenses, etc.), so the resource is identifiable. However, the vocabulary is heavily domain-specific and cryptic ("bands," "chain," "kehr," "bandmaster") with no gloss, and the description never distinguishes this tool from the sibling `workshop` or `bureau_look` tools, leaving the agent to infer which one to open.

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?

The description maps each `what` value to roughly what it returns, but offers no guidance on when to pick this tool over `workshop` or `bureau_look`, no prerequisites, and no statement of what happens after a failed lookup. The only conditional guidance is embedded in the `keep` clause (it walks the chain and keeps a link), which explains that single view but not the overall use policy.

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