Skip to main content
Glama

get_all_usage_stats

Retrieve comprehensive usage statistics for all sessions on the Healthcare MCP Server to monitor and analyze tool engagement effectively.

Instructions

Get overall usage statistics for all sessions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function getAllUsageStats() that executes the tool logic, returning overall usage statistics including session start time, total tool calls, and per-tool usage counts.
    getAllUsageStats() {
      return {
        status: 'success',
        overall_stats: {
          session_start: this.usageStats.session_start,
          total_calls: this.usageStats.total_calls,
          tool_usage: { ...this.usageStats.tool_usage }
        }
      };
    }
  • Registers the get_all_usage_stats tool in the MCP server's ListTools response, including its name, description, and input schema (empty object since no parameters required).
      name: "get_all_usage_stats",
      description: "Get overall usage statistics for all sessions",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Dispatch logic in the MCP CallTool request handler that routes execution of get_all_usage_stats to the usageService.getAllUsageStats() method.
    case "get_all_usage_stats":
      result = usageService.getAllUsageStats();
      break;
  • Dispatch logic in the HTTP server's handleCallTool function that routes get_all_usage_stats calls to usageService.getAllUsageStats().
    case 'get_all_usage_stats':
      return usageService.getAllUsageStats();
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets' data, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns aggregated or raw data, or any other behavioral traits. This leaves significant gaps for a tool that likely accesses usage data.

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, clear sentence with no wasted words. It front-loads the key action and resource, making it highly efficient and easy to parse for an AI agent.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'overall usage statistics' includes (e.g., metrics, time frames, format) or behavioral aspects like data freshness or access controls. For a tool that likely returns complex data, this leaves too much undefined.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, aligning with the schema. A baseline of 4 is applied since it doesn't add unnecessary details, though it could briefly note the lack of parameters for clarity.

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 verb ('Get') and resource ('overall usage statistics for all sessions'), making the purpose immediately understandable. It doesn't differentiate from its sibling 'get_usage_stats', which appears to be a similar tool, so it doesn't reach the highest score for sibling distinction.

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 like 'get_usage_stats' or other siblings. It lacks context about prerequisites, timing, or comparisons, leaving the agent to infer usage based on the name alone.

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

Related 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/Cicatriiz/healthcare-mcp-public'

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