Pickly

Answer a request to vote

review_voter_request

Destructive

On a poll that shows who voted, add someone who asked to be on the list of names, or turn them down (needs the manage key). Check with the person before deciding for them.

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": {
      "poll": "<poll>",
      "manageKey": "<manageKey>",
      "requestId": "<requestId>",
      "approve": "<approve>"
    },
    "name": "review_voter_request"
  }
}

Input Schema

Name	Required	Description
`poll`	Yes	The poll's link (https://usepickly.com/p/…) or its id.
`approve`	Yes	true adds the name to the poll's list so they can vote; false turns it down.
`manageKey`	Yes	The manage key create_poll returned for this poll.
`requestId`	Yes	The request's id, from get_results.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag this as destructive and non-idempotent, so the description's job is to add context, and it does: it discloses the manage-key authorization requirement and the fact that a decision affects a real person's access, advising confirmation first. It does not say whether a decision can be reversed, which would have completed the picture.

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?

Two short sentences, front-loaded with the operation and its scope, followed by the single most important behavioral caution. Nothing is redundant.

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 four-required-parameter mutation with annotations and no output schema, the description covers purpose, authorization, both outcomes, and a safety caution. It stops short of saying what happens to the requester or whether a decision can be changed later.

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 poll, approve, manageKey and requestId are already documented in the schema, including where requestId comes from. The description only echoes the manage-key requirement and the two approve outcomes, adding no syntax or edge-case meaning 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 names a specific verb pair ('add someone ... or turn them down') against a specific resource ('a request to vote' / 'the list of names'), and scopes it to 'a poll that shows who voted'. That scope distinguishes it from review_suggestion and get_results, though no sibling is named explicitly.

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?

It supplies a prerequisite ('needs the manage key') and a procedural caution ('Check with the person before deciding for them'), which is useful guidance. However, it never states when to prefer this over review_suggestion or get_results, so routing against the sibling tools is left to inference.

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

All Pickly tools Inspect

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

Need Help?