FeatureOS

Search feature requests

search_feature_requests

Read-only

Search feature requests (posts) by keyword or meaning.

Returns matching posts and a url_schema template (e.g. 'https://.../p/:slug'). To link to a post, replace :slug in the schema with the post's slug field.

Returns the top matching posts. To browse or filter a board without a query, use list_feature_requests instead. Use get_feature_request with a returned id for the full post.

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": {
      "query": "<query>"
    },
    "name": "search_feature_requests"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	The search query string. Semantic search over post title and description.

Output Schema

Name	Required	Description	Default
`page`	No
`has_more`	No
`per_page`	No
`url_schema`	No
`feature_requests`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds value by disclosing that results are capped ('returns the top matching posts') and explaining the url_schema template and how to substitute :slug. It does not discuss ranking/relevance behavior or result limits numerically, which keeps it from a 5.

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?

Front-loaded with purpose, then return shape, then sibling routing — a sensible order with no filler sentences. The url_schema paragraph is useful but slightly longer than necessary given an output schema already exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with a full output schema and strong annotations, nothing an agent needs is missing: purpose, result shape, result cap, slug substitution, and both escape hatches to sibling tools are all covered.

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% and the single parameter is fully documented in the schema itself. The description only adds the 'keyword or meaning' framing, which is a mild gloss on the schema's 'semantic search' note rather than new semantics. Baseline 3 applies.

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 ('Search feature requests (posts)') plus the matching dimension ('by keyword or meaning'), and explicitly contrasts with list_feature_requests and get_feature_request so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-not and alternatives: browse or filter a board without a query goes to list_feature_requests, and fetching a full post goes to get_feature_request with a returned id. Both the exclusion and the follow-up path are named.

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.