Skip to main content
Glama

get_cache_stats

Retrieve cache statistics to monitor server performance and optimize resource usage for Islamic text queries.

Instructions

Get cache statistics for monitoring server performance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that implements the get_cache_stats tool logic by collecting and returning statistics from all caching services (tafsir, hadith, quran, recitation, search).
    export function getAllCacheStats() {
      return {
        tafsir: getTafsirCache().getStats(),
        hadith: getHadithCache().getStats(),
        quran: getQuranCache().getStats(),
        recitation: getRecitationCache().getStats(),
        search: getSearchCache().getStats(),
      };
    }
  • Tool registration/dispatch in the executeTool switch statement, which calls the getAllCacheStats handler when 'get_cache_stats' is invoked.
    case 'get_cache_stats': {
      result = getAllCacheStats();
      break;
    }
  • MCP tool definition including name, description, and empty input schema (no parameters required).
    {
      name: 'get_cache_stats',
      description: 'Get cache statistics for monitoring server performance.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe important behavioral aspects: whether this requires admin permissions, what specific statistics are returned, if it's a real-time snapshot or aggregated data, potential performance impact, or error conditions. The description is functional but lacks operational context.

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 a single, efficient sentence that communicates the core purpose without unnecessary elaboration. It's front-loaded with the main action and resource, and the 'for monitoring server performance' clause adds useful context without redundancy. Every word earns its place in this compact description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a monitoring tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what statistics are returned, their format, units, or interpretation. For a tool that presumably returns structured performance data, users need to understand what metrics to expect. The description leaves too much unspecified about the tool's output and operational characteristics.

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 zero parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist. It correctly focuses on the tool's purpose rather than attempting to document non-existent inputs. This meets the baseline expectation for parameterless tools.

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 action ('Get') and resource ('cache statistics') with a specific purpose ('for monitoring server performance'). It distinguishes from siblings by focusing on system metrics rather than Quran/Hadith content retrieval. However, it doesn't explicitly contrast with potential alternative monitoring tools.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'monitoring server performance' as a general context but doesn't specify prerequisites, frequency, or comparison with other monitoring approaches. No explicit when/when-not statements or named alternatives are provided.

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/Prince77-7/quranMCP'

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