Dutify

fr_list_requests

Read-onlyIdempotent

List feature requests on a feedback board (by board slug). Filter by status / category / milestone name (lenient — trimmed + case-insensitive). Pass q to search request titles instead. Paginated via page/size. API-key scope: feedback:requests:read.

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": {
      "boardSlug": "<boardSlug>"
    },
    "name": "fr_list_requests"
  }
}

Input Schema

Name	Required	Description
`q`	No	Title search query (ignores other filters when set)
`page`	No	Zero-based page number (default 0)
`size`	No	Page size (default 20, max 200)
`status`	No	Status name filter (e.g. "In Progress")
`account`	No	Multi-account auth only: name of the account from X-Dutify-Accounts to use for this call. Ignored in single-account mode (X-API-Key header). When multiple accounts are configured and this is omitted, the call fails with ACCOUNT_REQUIRED listing the available names. list_accounts never requires a selection.
`category`	No
`boardSlug`	Yes	Board slug (from list_boards)
`milestone`	No
`workspace`	No	Workspace identifier or exact name for this call. Overrides the configured workspace. For personal keys, discover candidates with list_workspaces and select explicitly. Does not change other calls or expand a workspace key's access.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description still adds real behavior: lenient trimmed/case-insensitive matching, pagination via page/size, `q` overriding other filters, and the required API-key scope. It doesn't describe the response item shape, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short clauses, front-loaded with the core action, then filters, search mode, pagination, and auth scope. No filler; each sentence carries distinct information.

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 read-only paginated list with no output schema, the description covers filtering, search semantics, pagination, and auth scope. The only gap is return-shape/envelope detail, which is minor since readOnly list tools are predictable and account/workspace params are documented in the schema.

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?

With 78% schema coverage, baseline is 3, but the description adds meaning the schema lacks: the lenient normalized matching semantics for status/category/milestone (category and milestone have no schema descriptions at all) and the precedence rule for `q`. That meaningfully compensates for the coverage gap.

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 ('List feature requests') plus scope ('on a feedback board (by board slug)'), which clearly separates it from fr_list_bugs and the fr_get_* siblings. An agent can identify it without opening the 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?

Gives explicit guidance on the two modes: filter by status/category/milestone, or pass `q` to search titles instead. It stops short of naming sibling alternatives (e.g. fr_get_request for a single item), so it's clear context without full routing.

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

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