OohWeGo

Vote for a community post

vote_community_post

Votes for a post as the user (a bug they have too, an idea they want), or takes the vote back. Voting follows it.

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": {
      "postId": "<postId>",
      "voted": "<voted>"
    },
    "name": "vote_community_post"
  }
}

Input Schema

Name	Required	Description	Default
`voted`	Yes
`postId`	Yes	A community post’s id, from search_community

Output Schema

Name	Required	Description	Default
`post`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The description provides high-level behavioral context by framing the post as either a 'bug' or an 'idea.' This informs the agent about the nature of the content it is interacting with, a behavioral detail not found in the schema or annotations.

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?

The definition is extremely concise and uses efficient syntax, bundling the required use case examples in parentheses to maximize information density.

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?

Given the simplicity of the schema (two required parameters), the definition is highly complete. It clearly explains the 'why' of the action and the effect of the toggle, which is sufficient for accurate invocation.

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

Parameters4/5

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

While schema coverage is moderate, the description effectively clarifies the semantic meaning of the boolean 'voted' parameter—that it represents a toggle action (voting vs. taking the vote back). This is crucial for the agent to correctly set this parameter.

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 explicitly states the action (votes/takes the vote back) and the resource (a post), clearly defining its primary function. While it avoids defining its own scope against siblings, the specific action and context help differentiate it from similar tools like following.

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?

The description provides useful context by specifying the intent for voting (a bug they have too, an idea they want). However, it lacks explicit instructions on when to use this tool versus other potential alternatives, beyond describing the supported post types.

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

All OohWeGo 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?