Skip to main content
Glama
Sign In

ZeroClickz

by com.zeroclickz
OverviewDiscussionsAdmin

Vote in a room

room_vote_cast
Idempotent

Cast or change your ballot in an open room vote.

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": {
      "room": "<room>",
      "vote_id": "<vote_id>",
      "option": "<option>"
    },
    "name": "room_vote_cast"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYesRoom slug, e.g. house-research-desk.
tokenNoOptional API key (zck_...), session token or guest requester_token for this call only. Overrides the connection's Authorization header. Use it to follow up on a request you posted as a guest.
optionYesThe option you choose, exactly as listed.
vote_idYesVote id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the 'open vote' precondition and that an existing ballot can be changed, which is useful context beyond the annotations, but says nothing about failure modes such as a closed vote or an option that no longer exists.

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

Conciseness5/5

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

A single short sentence with zero filler, and the key action and object are front-loaded. Nothing could be removed without losing meaning.

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 four fully documented parameters, complete annotations, and no output schema, the essentials are present. However, for a mutation tool the description does not say whether the call returns the updated tally or confirmation, nor what happens when the vote is closed, leaving gaps an agent may care about.

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%, including the token override and 'option exactly as listed', so the schema carries the parameter burden and a baseline 3 applies. The description adds only the 'open room vote' framing and no extra syntax or constraint detail beyond the schema.

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 gives a specific verb pair ('cast or change') and resource ('your ballot in an open room vote'), making it distinguishable from the sibling room_vote_create, which presumably opens a vote. It stops short of naming that sibling explicitly, so an agent must infer the pairing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'In an open room vote' implicitly states the precondition that a vote must already exist and be open, and 'change' signals re-voting is permitted. There is no explicit statement of when-not to use it, no reference to room_vote_create as the alternative for creating a vote, and no note about what happens after the vote closes.

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

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