Skip to main content
Glama
Sign In
mcp-ispkeeper

mcp-ispkeeper

by ssservicios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_clients_summary

Retrieve a quick summary of total and active client counts to monitor ISP customer base at a glance.

Instructions

Get a quick summary of total and active client counts. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead.

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_clients_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

Without annotations, the description must disclose behavior. It clearly states the tool is read-only (no mutation) and includes a strong honesty directive to avoid hallucination. This adds trustworthy behavioral context beyond the schema.

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 extremely concise with two well-structured sentences. The warning is front-loaded with an emoji for attention, making it efficient and scannable.

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?

Given the tool is parameterless and has no output schema, the description is nearly complete. It explains the behavior (read-only), the expected output (summary counts), and provides a fail-safe instruction. The only minor gap is not specifying the time period or criteria for 'active'.

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?

Schema coverage is 100% with 0 parameters, so no explanation is needed. The description adds meaning by specifying the output content (total and active client counts), which is helpful.

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 specifies the verb 'Get' and the resource 'a quick summary of total and active client counts', making the purpose clear. It does not explicitly differentiate from siblings like 'search_clients' or 'get_client', but the mention of 'summary' implies a broader, aggregative function.

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

Usage Guidelines3/5

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

The description provides a usage note about not fabricating data on failure, but does not explain when to use this tool over siblings. The summary nature is implied, but explicit guidance on when not to use it or alternatives is missing.

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