Skip to main content
Glama

Get Full Cached Metadata

get_metadata_full
Read-onlyIdempotent

Retrieve comprehensive MantisBT metadata including all projects with full details, user lists, versions, categories, and tags. Automatically syncs if cache is outdated.

Instructions

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 sync_metadata to force a refresh. For a lightweight overview use get_metadata instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'get_metadata_full', which loads metadata from the cache or fetches and caches it if missing or invalid, then returns the full metadata as a JSON string.
      async () => {
        try {
          const data: CachedMetadata = await cache.loadIfValid() ?? await fetchAndCacheMetadata(client, cache);
          return {
            content: [{ type: 'text', text: JSON.stringify(data) }],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
        }
      }
    );
  • Registration of the 'get_metadata_full' tool, including its schema and description.
      server.registerTool(
        'get_metadata_full',
        {
          title: 'Get Full Cached Metadata',
          description: `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 sync_metadata to force a refresh. For a lightweight overview use get_metadata instead.`,
          inputSchema: z.object({}),
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
          },
        },
Behavior4/5

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

Annotations establish read-only/idempotent safety profile. Description adds critical behavioral context not in annotations: 24-hour TTL expiration policy, automatic sync side-effect on cache miss, and detailed breakdown of what 'complete' entails (raw cache structure with per-project lists). Could mention performance implications of fetching full cache, but adequately covers main behavioral traits.

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?

Three sentences with zero waste: sentence 1 defines return payload, sentence 2 explains caching/sync behavior, sentence 3 provides sibling alternatives. Information is front-loaded with the most critical detail (what it returns) and maintains tight focus on actionable guidance.

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?

No output schema exists, so description appropriately compensates by enumerating the complete data structure returned (projects, users, versions, categories, tags). Given the tool's purpose as a comprehensive cache dump, this enumeration provides sufficient context for selection, though specific data types or nesting structure would elevate this further.

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?

Input schema contains zero parameters (empty object). Per rubric, zero parameters establishes baseline score of 4. Description appropriately requires no parameter clarification since the tool takes no arguments.

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?

Description uses specific verb 'Return' with clear resource scope ('complete raw MantisBT metadata cache') and enumerates exact contents (projects with full fields, users, versions, categories, tags). Explicitly distinguishes from sibling 'get_metadata' by contrasting 'full' vs 'lightweight overview' and from 'sync_metadata' by contrasting automatic vs forced refresh.

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?

Provides explicit when-to-use alternatives: 'Use sync_metadata to force a refresh' and 'For a lightweight overview use get_metadata instead.' Also clarifies implicit usage condition regarding automatic synchronization when cache is expired or missing, giving clear decision criteria between the three related tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dpesch/mantisbt-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server