FeatureOS

List downvoters

list_downvoters

Read-only

List all downvoters, optionally filtered by feature request and date range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_downvoters"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default: 1).
`to_date`	No	Filter votes until this date (YYYY-MM-DD). Use with from_date for a date range.
`from_date`	No	Filter votes from this date (YYYY-MM-DD). Use with to_date for a date range.
`feature_request_id`	No	Filter by a specific feature request ID.

Output Schema

Name	Required	Description	Default
`page`	No
`votes`	No
`has_more`	No
`per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the filtering behavior but says nothing about pagination limits or result volume, which matters for a list endpoint.

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?

A single well-formed sentence with the optionality constraint front-loaded; no filler, no redundancy.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The only meaningful gap is pagination expectations, which the description leaves entirely to the schema's page parameter.

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 coverage is 100%, so every parameter is already documented including date format and the from/to pairing rule. The description only restates the filter dimensions at a high level, adding no new semantics 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?

States a specific verb+resource ("List all downvoters") and adds scope via optional filters by feature request and date range. It does not explicitly distinguish itself from the sibling list_upvoters, though the resource name makes the opposite-direction counterpart obvious.

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 word "optionally" makes clear all filters are optional and implies the tool can be called with no arguments, but it gives no guidance on when to use this versus list_upvoters or get_feature_request for vote inspection.

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

All FeatureOS 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.