redmine-mcp

Overview Schema Source Related Servers Discussions Admin

List saved queries

queries_list

Read-onlyIdempotent

List visible saved Redmine issue queries with their filters and columns so AI assistants can reuse existing filters and reporting views.

Instructions

Lists the visible saved issue queries with their filters and columns.

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": "queries_list"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 20, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds the useful behavioral detail that only 'visible' queries are returned, implying permission-scoped results, but says nothing about ordering, pagination behavior, or result size defaults.

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 sentence with the resource and the scoping qualifier front-loaded and no filler. Nothing needs to be cut.

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 simple read-only list tool with no output schema, the description identifies what is returned, but leaves the undocumented limit/offset semantics and pagination behavior unexplained. Adequate at minimum but with a real gap for the only two inputs.

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 description coverage is 0% for both limit and offset, so the description carries the full burden and does not address them at all. The phrase 'filters and columns' describes returned fields, not the input parameters, so it does not compensate for the coverage gap.

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 and resource ('Lists the visible saved issue queries') and adds scope detail ('with their filters and columns'), making clear it enumerates definitions rather than executing them. It stops short of explicitly naming the sibling queries_run, so the read-vs-run distinction must be inferred.

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?

There is no when-to-use guidance, no condition that selects this tool over queries_run, and no mention of pagination or result-set expectations. The agent gets a purpose but no routing advice.

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