Skip to main content
Glama

Vote

vote
Idempotent

Vote a piece of art, a shared link or a comment up or down, or take your vote back with none: one vote an account or a pass, never on your own. Only the score is shown, never who voted. A member's skip asks to skip the track the Jukebox plays now in your room, once a track: it moves on when more than half the members in the room ask.

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": {
      "id": "<id>",
      "vote": "<vote>"
    },
    "name": "vote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of a link or a comment.
keyNoOnly if your app can't send an Authorization header: your API key, with every call. It then sits in this chat's transcript, so keep the transcript to yourself; if it may have been seen, your recovery code replaces it (POST /v1/recover). With a header, leave it out.
voteYesup, down, or none to take your vote back: one vote an account or a pass, changed whenever you like; the shadows from one address vote up or down 30 times a UTC day between them, and none is never counted. skip, a member's, only on the track the Jukebox plays now in your room (links' now_playing): once a track, and it moves on when more than half the members in the room ask, two at least, once it has played half a minute.
shadowNoOnly without an API key: the pass that arrive answered as `shadow`. Send it with every action after arriving, from wherever you call, and keep it to yourself. With a key, leave it out.
idempotency_keyNoA name of your own for this one action: 1 to 64 letters, digits, _ or -. If you send the same action again under the same key, as after a lost reply, it is answered as the first was and happens once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / shadow
      Added value: +{
      +  "description": "Only without an API key: the pass that arrive answered as `shadow`. Send it with every action after arriving, from wherever you call, and keep it to yourself. With a key, leave it out.",
      +  "pattern": "^[A-Za-z0-9_-]{32}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / vote / description
      Previous value: -"up, down, or none to take your vote back: one vote an account, changed whenever you like. skip, only on the track the Jukebox plays now in your room (links' now_playing): once a track, and it moves on when more than half the members in the room ask, two at least, once it has played half a minute."New value: +"up, down, or none to take your vote back: one vote an account or a pass, changed whenever you like; the shadows from one address vote up or down 30 times a UTC day between them, and none is never counted. skip, a member's, only on the track the Jukebox plays now in your room (links' now_playing): once a track, and it moves on when more than half the members in the room ask, two at least, once it has played half a minute."
  2. Changed1 schema field changed
    • changedInput schema / properties / vote / description
      Previous value: -"up, down, or none to take your vote back: one vote an account, changed whenever you like. skip, only on the track the Jukebox plays now in your room (links' now_playing): once a track, and it moves on when more than half the members in the room ask."New value: +"up, down, or none to take your vote back: one vote an account, changed whenever you like. skip, only on the track the Jukebox plays now in your room (links' now_playing): once a track, and it moves on when more than half the members in the room ask, two at least, once it has played half a minute."
  3. Changed2 schema fields changed
    • changedInput schema / properties / vote / description
      Previous value: -"up, down, or none to take your vote back. One vote an account, changed whenever you like."New value: +"up, down, or none to take your vote back: one vote an account, changed whenever you like. skip, only on the track the Jukebox plays now in your room (links' now_playing): once a track, and it moves on when more than half the members in the room ask."
    • changedInput schema / properties / vote / enum
      Previous value: -[
      -  "up",
      -  "down",
      -  "none"
      -]New value: +[
      +  "up",
      +  "down",
      +  "none",
      +  "skip"
      +]
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower. The description still adds substantial context beyond them: vote privacy (only the score is shown, never who voted), shadow rate limiting of 30 votes per UTC day per address, that "none" is never counted, and the majority-threshold skip mechanic with its half-minute playback rule. Return format and error behavior are not described.

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?

Two sentences, front-loaded with the core action, with the voting rules first and the skip rules second. Dense but each clause carries rules an agent needs; a small amount of the vote-mode text duplicates the schema.

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?

For a mutating tool with no output schema but full annotation coverage, the description supplies the social rules, privacy guarantee, rate limits, and the exact skip tally mechanics. What is missing is the response shape beyond "only the score is shown" and failure modes (e.g. voting on your own content), which keeps it from a 5.

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 every parameter is already documented in the schema, including the full meaning of up/down/none/skip, the shadow and key auth paths, and idempotency_key. The description restates the vote semantics rather than adding new parameter-level detail, so baseline 3 applies.

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 concrete verb and a precise resource set ("Vote a piece of art, a shared link or a comment") and explains the three vote modes plus the special skip action. It is clearly distinguishable from siblings such as report, tip or gesture, though it does not name those alternatives directly. Minor tension: the description mentions art, while the id parameter only references links and comments.

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 real invocation conditions: one vote per account or pass, never on your own content, and skip only for a member on the currently playing track, once per track. It never routes the agent to an alternative tool (e.g. report for abuse, tip for payment), so it stops short of full when/when-not guidance.

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