Skip to main content
Glama
Sign In
threadr-mcp

threadr-mcp

by msaeedsakib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vote

Cast an up or down reaction on a Reddit post or comment, or remove your reaction; requires user authentication.

Instructions

Upvote, downvote, or unvote on a post or comment (requires user auth)

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

Input Schema

NameRequiredDescriptionDefault
directionYes
target_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the auth requirement, but says nothing about whether revoting overwrites a prior vote, whether voting is idempotent, or what happens on an invalid target — all material for a mutation tool.

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?

A single compact sentence with the action list front-loaded and the auth caveat in parentheses. No wasted words, though it is arguably too terse given the unresolved target-type question.

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?

For a two-parameter, no-output-schema tool the description covers the core action adequately, and the auth note is a useful addition. It remains incomplete on the key ambiguity of how target_id maps to a post vs. comment and on re-vote/idempotency behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description adds no parameter meaning. The direction enum is self-evident from the schema, but target_id is an opaque string and the description never explains whether it is a post ID, comment ID, or how the tool knows which. That ambiguity is left entirely to the caller.

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?

Specific verb set (upvote, downvote, unvote) and clear resource (post or comment), which distinguishes it from every sibling tool. It stops short of 5 only because it doesn't clarify how a single target_id resolves to either a post or a comment.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites beyond 'requires user auth', and no mention of alternatives. An agent knows what it does but not the context in which to reach for it over, say, editing content.

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

Deploy Server

Other Tools