Skip to main content
Glama

get_collection_cache_health

Monitor cache performance and identify issues with offline browsing capability by checking health status and statistics for the collection cache system.

Instructions

Get health status and statistics for the collection cache system. This helps monitor cache performance and identify any issues with offline browsing capability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration including name, description, empty input schema, and handler lambda delegating to server.getCollectionCacheHealth()
    {
      tool: {
        name: "get_collection_cache_health",
        description: "Get health status and statistics for the collection cache system. This helps monitor cache performance and identify any issues with offline browsing capability.",
        inputSchema: {
          type: "object",
          properties: {}
        }
      },
      handler: () => server.getCollectionCacheHealth()
    }
  • The MCP tool handler function, which calls the server's getCollectionCacheHealth method
    handler: () => server.getCollectionCacheHealth()
  • TypeScript interface definition for the server method called by the tool handler
    getCollectionCacheHealth(): Promise<any>;
  • Core cache statistics computation for collection cache health: item count, age, and validity status
    async getCacheStats(): Promise<{ itemCount: number; cacheAge: number; isValid: boolean }> {
      const cache = await this.loadCache();
      if (!cache) {
        return { itemCount: 0, cacheAge: 0, isValid: false };
      }
      
      return {
        itemCount: cache.items.length,
        cacheAge: Date.now() - cache.timestamp,
        isValid: Date.now() - cache.timestamp <= this.CACHE_TTL_MS
      };
    }
  • Aggregated cache health stats from both index and collection caches, likely the data returned by getCollectionCacheHealth()
    async getCacheStats(): Promise<any> {
      const indexStats = this.indexCache.getCacheStats();
      const cacheStats = await this.collectionCache.getCacheStats();
      
      return {
        index: indexStats,
        collection: cacheStats
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions the tool helps with monitoring and identifying issues, it doesn't describe what the tool actually returns (e.g., metrics, error states), whether it requires specific permissions, or any rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 description is two sentences that are front-loaded and efficient. The first sentence states the core purpose, and the second adds context without redundancy. Every sentence earns its place by providing clear value, making it appropriately sized and well-structured.

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 tool has no parameters (simplifying input) but no output schema (complicating output understanding), the description is moderately complete. It explains what the tool does and why to use it, but it lacks details on what the health status and statistics include, which is critical for a monitoring tool. With no annotations and no output schema, more behavioral context would improve completeness.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to compensate for any gaps, and it appropriately doesn't discuss parameters. A baseline of 4 is applied since no parameter information is required, and the description focuses on the tool's purpose instead.

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?

The description clearly states the tool's purpose: 'Get health status and statistics for the collection cache system.' It specifies the verb ('Get') and resource ('health status and statistics for the collection cache system'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_build_info' or 'portfolio_status', which might also provide system status information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides implied usage context: 'This helps monitor cache performance and identify any issues with offline browsing capability.' This suggests when to use the tool (for monitoring and troubleshooting), but it doesn't explicitly state when not to use it or name alternatives among the many sibling tools. The guidance is helpful but not comprehensive.

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/DollhouseMCP/DollhouseMCP'

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