Skip to main content
Glama

get_stats

Retrieve session statistics and current configuration snapshot from the prompte-mcp server to monitor prompt enhancement performance and settings.

Instructions

Get session totals and current config snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'get_stats' tool which returns session stats, per-technique stats, and current configuration.
    case 'get_stats': {
      const { stats } = getStats();
      return { session: sessionStats, perTechnique: stats, config: getConfig() };
    }
  • Helper function that reads and returns the statistics from the decisions file.
    export function getStats() {
      return readJSON(DECISIONS_FILE, { decisions: [], stats: {} });
    }
Behavior2/5

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

Zero annotations provided, so description carries full behavioral burden. Only states what is retrieved without disclosing side effects, caching behavior, cost/heaviness of the operation, or session scope definition. Merely implies read-only nature through 'Get'.

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?

Single efficient sentence of seven words with zero redundancy. Information is front-loaded and immediately actionable.

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?

Minimal viable completeness for a zero-parameter tool. Description identifies the two data domains (session stats, config) but lacks detail on what 'session totals' comprises or the snapshot format, which would help given no output schema exists.

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 has zero parameters (confirmed by context signals), triggering baseline score of 4. Description does not need to compensate for missing parameter documentation.

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?

Uses specific verb 'Get' and identifies resources 'session totals' and 'current config snapshot'. Somewhat distinguishes from sibling get_config by including session metrics, though overlap with config retrieval isn't explicitly clarified.

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?

Provides no guidance on when to prefer this over get_config or other siblings, nor any prerequisites or conditions for use. Agent must infer applicability from the resource names 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

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/AlanRoybal/prompte-mcp'

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