Skip to main content
Glama
Sign In

QRvote

by org.qrvote
OverviewDiscussionsAdmin

Order printed posters on Zazzle: a ready order link and print image for each size

get_poster_orders
Read-onlyIdempotent

Order printed posters on Zazzle: a ready order link and print image for each size The poster from the dashboard's Print page, in the contest's language, with its QR code (it opens the public page only). orders maps each size (18x24 and 12x18 posters, 16x20 foam board) to a Zazzle link that opens that product filled in; give the person the link, and they order and pay on Zazzle. posters holds the print images. englishWords means the contest's language can't be printed yet, so the poster is in English. Sheets of entry signs aren't offered here: they carry entry codes, so they're ordered from the Print page. Needs the organizer key.

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": {
      "slug": "<slug>"
    },
    "name": "get_poster_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe id in the public link, e.g. `scarecrow-contest-2026-ab12` from https://qrvote.org/c/scarecrow-contest-2026-ab12
accentNoThe sign color as 6 hex digits, no #. Leave it out for the contest theme's color, as on the dashboard's Print page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / accent / description
      Previous value: -"The sign color as 6 hex digits, no # (e.g. 2446c8, the default blue). Use the contest theme's accent to match the dashboard's Print page."New value: +"The sign color as 6 hex digits, no #. Leave it out for the contest theme's color, as on the dashboard's Print page."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real signal on top: an organizer key is required, the links open the public page only, and `englishWords` flags that the contest language can't be printed so the poster falls back to English. It doesn't explain failure modes for a bad slug, which keeps it off 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.

Conciseness3/5

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

The opening clause simply repeats the title verbatim before getting to substance, and the body is a long run-on mixing outputs, fallback behavior, exclusions, and auth. The content is valuable but not front-loaded or cleanly separated, so the reader must parse it all to find what the tool returns.

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?

With no output schema, the description carries the return-value burden and does so: it names `orders`, `posters`, and `englishWords` and their meaning, plus the organizer-key requirement and the entry-sign exclusion. Only the auth-passing mechanics and error conditions are left implicit.

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 both params are well documented there, so the baseline is 3. The description adds no meaning about slug or accent (e.g. what accent does to the rendered poster) beyond the schema's own text.

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 names the concrete output: `orders` maps each poster size (18x24, 12x18, 16x20 foam board) to a pre-filled Zazzle link, and `posters` holds the print images, so the agent knows exactly what comes back. It also scopes out entry-sign sheets, which is a useful boundary. It doesn't compare against any named sibling tool, keeping it just 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?

It gives clear operating context: give the link to the person and they complete and pay on Zazzle, and it states that entry-sign sheets are ordered elsewhere (the Print page). What's missing is any explicit tie-break against the many sibling tools (e.g. get_dashboard or get_certificate_orders) for agents deciding where to start.

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

All QRvote 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