Pickly

Review a suggested option

review_suggestion

Destructive

Approve or turn down an option a voter suggested on a poll this chat made (it needs the manage key). Approved suggestions become options everyone can vote on. 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>",
      "suggestionId": "<suggestionId>",
      "approve": "<approve>"
    },
    "name": "review_suggestion"
  }
}

Input Schema

Name	Required	Description
`poll`	Yes	The poll's link (https://usepickly.com/p/…) or its id.
`approve`	Yes	true adds it to the poll as an option; false turns it down. Either is final.
`manageKey`	Yes	The manage key create_poll returned for this poll.
`suggestionId`	Yes	The suggestion's id, from get_results.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already flag destructiveHint=true and idempotentHint=false, so the safety bar is partly met. The description adds value beyond them by explaining the downstream consequence ('Approved suggestions become options everyone can vote on') and the authorization prerequisite (manage key), which an agent needs before acting.

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?

Three short sentences with the action and scope front-loaded, followed by consequence and then the caution. No repetition of the schema and no filler.

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 no output schema and destructive annotations, the description covers purpose, authorization, consequence, and a confirmation caution. Only a note on what happens to the poll state or how outcomes surface to the caller is missing.

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 including the approve/deny boolean and its finality is already documented in the schema. The description reinforces the manage-key requirement but adds no syntax or format detail beyond what the schema provides, 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 specific verb pair ('Approve or turn down') and a precise resource ('an option a voter suggested on a poll this chat made'), which is clearly distinct from the sibling review_voter_request. It falls short of 5 only because it never names or contrasts that sibling explicitly.

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 usage context: the operation requires the manage key, and the agent should check with the person before deciding on their behalf. It does not name an alternative tool or an explicit when-not condition, so it stops short of full routing guidance.

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?