Skip to main content
Glama
Sign In
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Full Cached Metadata

get_metadata_full
Read-onlyIdempotent

Return all MantisBT metadata in one cache—projects, users, versions, categories, and tags—auto-syncing when missing or expired.

Instructions

Deprecated: use get_metadata with detail: "full" instead — get_metadata_full will be removed in 2.0.0.

Return the complete raw MantisBT metadata cache: all projects with full fields, and per-project lists of users, versions, categories, plus all tags.

If the cache does not exist or has expired (default TTL: 24 hours), it will automatically sync first. Use get_metadata with refresh: true to force a refresh.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv1.10.4
  3. Removed
  4. Addedv1.5.15

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly, idempotent, and non-destructive annotations, the description discloses cache expiration behavior via a default 24-hour TTL and automatic sync when the cache is missing or expired. It also gives the deprecation lifecycle and removal version, which materially affects agent behavior.

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?

The deprecation warning is front-loaded, followed by a concise description of returned data, cache behavior, and refresh guidance. Every sentence supplies actionable information for selecting or avoiding the tool.

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?

There is no output schema, but the description adequately explains the returned content as the full metadata cache with all projects and per-project users, versions, categories, plus tags. Combined with the annotations and the zero-parameter schema, the definition is complete for correct invocation or avoidance.

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?

This tool has zero parameters, so there is no tool-specific parameter semantics to explain. The description references detail: "full" and refresh: true only for the replacement get_metadata tool, which is useful but not a parameter of this tool.

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 uses a specific verb and resource: it returns the complete raw MantisBT metadata cache, including projects, users, versions, categories, and tags. It also explicitly names the replacement tool and parameter combination, which distinguishes it from get_metadata and sync_metadata.

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?

Usage is explicit: the tool is deprecated, should be replaced by get_metadata with detail: "full", and will be removed in 2.0.0. It also states when automatic syncing happens and how to force a refresh with get_metadata refresh: true.

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