Skip to main content
Glama

Upvote a heistclips feature request

upvote_feature_request
Idempotent

Adds one upvote to a request on the heistclips board, by id from list_feature_requests. One vote per caller; repeat calls do not add more.

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>"
    },
    "name": "upvote_feature_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequest id from list_feature_requests

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false and idempotentHint=true; the description reinforces the idempotency with a caller-scoped rule ('One vote per caller; repeat calls do not add more'), which is useful because it explains what repeated calls actually return in effect. It doesn't cover failure behavior for an invalid id, but it adds real context beyond the structured fields.

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 action and target, then the id source and the per-caller vote limit. No wasted wording.

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 one-parameter mutation with full annotation coverage and no output schema, the definition supplies the action, the id provenance, and the idempotency rule. Only minor gaps remain, such as what happens when the id is unknown.

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 the single parameter is fully documented as 'Request id from list_feature_requests', which the description merely restates. No added syntax, format, or provenance details beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Adds one upvote to a request') plus the board it applies to, and names list_feature_requests as the source of the id, so an agent can tell it apart from request_a_feature without opening either schema.

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?

The description makes the usage context clear: it is for casting a vote on an existing request whose id comes from list_feature_requests. It doesn't explicitly exclude creating a new request (request_a_feature), but the 'by id' constraint makes the intended path unambiguous.

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.