Skip to main content
Glama
MCP Prompts Server

MCP Prompts Server

by sparesparrow

Library statistics

get_stats
Read-onlyIdempotent

Retrieve counts of prompts, templates, tags, and categories, plus storage status showing whether changes are saved to disk.

Instructions

Counts of prompts and templates, the tags and categories in use, and whether changes are saved to disk (storage).

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": "get_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
tagsYes
totalYes
regularYes
sourcesYes
storageYes
templatesYes
categoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.1.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "categories": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "regular": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "sources": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "bundled": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "catalog": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "session": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "user": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "bundled",
      +        "catalog",
      +        "user",
      +        "session"
      +      ],
      +      "type": "object"
      +    },
      +    "storage": {
      +      "enum": [
      +        "memory",
      +        "file"
      +      ],
      +      "type": "string"
      +    },
      +    "tags": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "templates": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "total": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "templates",
      +    "regular",
      +    "tags",
      +    "categories",
      +    "storage",
      +    "sources"
      +  ],
      +  "type": "object"
      +}
  2. First observedv4.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful scope information (it reports counts, taxonomies, and whether changes persist to disk via `storage`), but says nothing about cost, freshness, or whether counts are live or cached. With annotations doing the heavy lifting, this is a modest but real contribution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence listing the payload components with zero filler, and the most important item (counts) is front-loaded. It reads as a fragment rather than a sentence, which slightly weakens the opening but wastes no words.

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 zero-parameter, read-only stats tool with an output schema and full annotation coverage, the definition supplies enough for correct invocation. Only the absence of explicit usage guidance keeps it from being fully complete.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The parenthetical naming `storage` is a nice touch that ties a returned field to a name, but no parameter meaning is at stake.

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 names the concrete contents returned: counts of prompts and templates, the tags and categories in use, and a `storage` persistence flag. That is specific enough to distinguish it from the prompt-CRUD siblings, though it is phrased as a noun list rather than an explicit verb+resource statement like 'Get library statistics'.

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?

There is no when-to-use guidance, no conditions, and no mention of alternatives among the siblings (list_prompts, get_prompt, etc.). The agent must infer that this is the aggregate/overview tool from the described payload alone.

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