Skip to main content
Glama

What Keel Stats Pro Includes

pro_plan
Read-onlyIdempotent

Use this when the user asks what Keel Stats Pro includes, what a paid account adds, or which of these tools need it. Returns the Pro features in a line each, the tools that need Pro and the ones where Pro adds to a free answer, and where to read more (with the price where the client shows one). Not for statistics: every other tool answers those.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds real value beyond them by describing the return content: features as one line each, which tools require Pro, which merely benefit, further-reading links, and price when the client surfaces it. Only minor gaps remain — nothing about formatting limits, but there is little behavior left to disclose for a static info tool.

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?

Three sentences, front-loaded with the trigger, then the return shape, then the exclusion. Every clause carries information an agent would otherwise have to guess, and nothing is repeated.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing return values and does so concretely (feature lines, tools requiring Pro, further reading, price). For a zero-parameter, read-only informational tool, nothing an agent needs in order to call it correctly is missing.

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 the baseline of 4 applies. There is nothing for the description to disambiguate, and it correctly spends no words on inputs.

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 states a specific verb and resource — it 'returns the Pro features in a line each, the tools that need Pro... and where to read more' — and closes by scoping out the entire statistical toolset ('Not for statistics: every other tool answers those'). An agent can tell immediately that this is the account/plan information tool, not an analytics tool.

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

Usage Guidelines5/5

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

It gives explicit trigger conditions ('when the user asks what Keel Stats Pro includes, what a paid account adds, or which of these tools need it') and an explicit exclusion with a redirect ('Not for statistics: every other tool answers those'). Both when-to-use and when-not are stated, so no inference is required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources