mcp-ispkeeper

list_subscription_catalog

Retrieve subscription plans, categories, or subcategories from ISPKeeper. Filter by text search, deleted records, or parent ID to find the needed catalog data.

Instructions

List the subscription catalog: plans, categories, or subcategories. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource": "<resource>"
    },
    "name": "list_subscription_catalog"
  }
}

Input Schema

Name	Required	Description
`q`	No	Text search (plans only)
`borrado`	No	Filter deleted records
`resource`	Yes	Catalog resource to list
`parent_id`	No	For plans: subcategory ID. For subcategories: category ID.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Sep 25, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds a useful failure-handling instruction ('NEVER fabricate data... report the error'), but it does not describe return format, pagination, filtering behavior, or other side effects. The warning provides some transparency but not comprehensive behavioral context.

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 one concise sentence followed by a relevant warning. It front-loads the action and resource scope, and every sentence earns its place. There is no unnecessary verbosity.

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?

The schema covers parameters well, and the description adds a failure-handling instruction, but there is no output schema and no guidance on how results are returned or when to prefer this over sibling tools. For a simple list operation, this is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters. The description adds no additional parameter-level meaning beyond restating the resource types, which are already captured in the resource enum. Baseline 3 is appropriate.

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 uses a specific verb ('List') and resource ('subscription catalog'), and enumerates the exact resource types: plans, categories, or subcategories. It is clear about what the tool does, though it does not explicitly differentiate itself from siblings like list_plans or list_subscriptions.

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 guidance on when to use this tool versus alternatives such as list_plans or list_subscriptions. The warning about not fabricating data is operational advice, not usage selection guidance, so the agent is left to infer the appropriate context.

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