Skip to main content
Glama
Sign In
PM-Skills MCP

PM-Skills MCP

by product-on-purpose
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pm_cache_stats

Retrieve cache performance metrics including hit rate, size, and TTL settings to monitor and debug server behavior.

Instructions

Get PM-Skills cache statistics.

Shows performance metrics for the skill content cache including hit rate, cache size, and TTL settings.

Useful for monitoring server performance and debugging cache behavior.

Returns: Markdown formatted cache statistics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pm_cache_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It details the return format ('Markdown formatted cache statistics') and the metrics included (hit rate, cache size, TTL settings). It could confirm the operation is read-only, but this is strongly implied.

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 three short sentences, each earning its place: purpose, metrics, usage context, and return format. No fluff, well-structured.

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?

For a simple read-only stats tool with no parameters, the description covers purpose, usage, and return format. It could mention whether the data is real-time, but overall it is sufficient for the tool's complexity.

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 zero parameters, so schema coverage is 100% trivially. The description adds value by explaining the return format, which compensates for a lack of output schema. No parameter information is needed.

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?

The description opens with 'Get PM-Skills cache statistics', which is a specific verb+resource combination. It clearly distinguishes from sibling tools, none of which are cache-related.

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

Usage Guidelines4/5

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

The description states the tool is 'Useful for monitoring server performance and debugging cache behavior', providing clear context. However, it does not explicitly mention when not to use it or alternatives, though none exist among siblings.

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

Deploy Server

Other Tools