Skip to main content
Glama
Sign In
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Issue Fields

get_issue_fields
Read-onlyIdempotent

Lists valid issue fields for the select parameter before constructing issue queries, based on this MantisBT server's active configuration. Deprecated: use get_issue_schema instead.

Instructions

Deprecated: use get_issue_schema instead — get_issue_fields will be removed in 2.0.0.

Return all field names that are valid for the "select" parameter of list_issues and get_issue.

Fields are discovered by fetching a sample issue from MantisBT (which reflects the server's active configuration — e.g. whether eta, projection, or profile fields are enabled) and merging the result with fields that MantisBT omits when empty (notes, attachments, relationships, etc.). The result is cached with the same TTL as the metadata cache.

Use this tool before constructing a "select" string to ensure you only request fields that exist on this server.

Input Schema

NameRequiredDescriptionDefault
project_idNoOptional project ID to scope the sample issue fetch

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / maximum
      Added value: +9007199254740991
  2. Addedv1.10.4
  3. Removed
  4. First observedv1.5.6

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses how results are produced (sample issue fetch reflecting server configuration such as eta/projection/profile toggles), that empty-by-default fields are merged in, and that output is cached with the metadata TTL. These are exactly the operational details annotations cannot carry.

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?

Deprecation and replacement are correctly front-loaded, and each following sentence carries distinct information (scope, discovery mechanism, caching). The discovery paragraph is somewhat dense but not redundant.

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?

With no output schema, the description does explain the content of the return value (field names valid for select) and the caching behavior. It stops short of describing the concrete response shape (list vs. object with metadata), which is the one thing an agent must infer.

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 optional project_id already documents its purpose (scoping the sample issue fetch). The description adds only indirect meaning via the mention of server configuration, so 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+resource (return all valid field names) and scopes it precisely to the "select" parameter of list_issues and get_issue. It also names its replacement (get_issue_schema) up front, so an agent can tell it apart from the sibling schema tool immediately.

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?

"Use this tool before constructing a 'select' string" gives an explicit trigger, and the deprecation line explicitly routes new callers to get_issue_schema. Both when-to-use and the alternative are stated, not implied.

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