Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by GonzaloRando03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_project_files

Retrieve all files attached to a Redmine project by providing its ID or identifier. Helps manage project attachments efficiently.

Instructions

Lists all files attached to a project (available since Redmine 3.4).

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": {
      "project_id": "<project_id>"
    },
    "name": "list_project_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID (numeric) or identifier (string)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description is the sole source of behavioral info. It only states the basic function, omitting details like authentication requirements, pagination, or whether it returns all files. This is a significant gap for a listing operation.

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?

Extremely concise: a single sentence that immediately states the purpose. No redundant or extraneous information, making it easy to parse quickly.

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?

Given the simplicity of the tool (one parameter, no output schema), the description is adequate but lacks details on return format or pagination. It meets the minimum for a straightforward list operation.

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?

The schema covers the single parameter fully (100% coverage), and the description does not add further meaning. Baseline 3 is appropriate as the description does not compensate beyond the schema.

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?

The description clearly states 'Lists all files attached to a project', specifying the action and resource. It also includes a version note for context, effectively distinguishing it from sibling tools like 'list_issues' or 'list_project_versions'.

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?

No explicit guidance on when to use this tool versus alternatives, such as when to use 'create_project_file' or search tools. The version mention is helpful but insufficient for guiding selection among siblings.

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

Deploy Server

Other Tools