calagopus-mcp

List panel API endpoints

calagopus_list_endpoints

Read-only

Search the live OpenAPI spec to find endpoints when no dedicated tool covers your need. Retrieve the exact path to call with calagopus_get.

Instructions

Search this panel's live OpenAPI spec for endpoints. Use it when no dedicated tool covers what you need, then call calagopus_get with the path you find. Reflects the panel's actual version, including routes added by extensions.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max paths to return.
`filter`	No	Case-insensitive substring to match against the path, e.g. 'backup'.
`method`	No	Only list paths that support this method. Defaults to get.	get

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the bar is lower. The description adds useful context about reflecting the panel's actual version and extension-added routes, but does not introduce any conflicting behavior.

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 two sentences, front-loaded with the primary action and purpose, and every sentence carries essential information without redundancy.

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?

Given the tool's simplicity (3 optional parameters, no output schema), the description is complete. It explains what the tool does, when to use it, and how to proceed after listing endpoints.

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?

The input schema covers 100% of parameters with clear descriptions, so the baseline is 3. The tool description does not add any extra parameter-specific explanation beyond the schema, but the schema itself is sufficient.

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 clearly states the tool lists panel API endpoints by searching the live OpenAPI spec, and it explicitly distinguishes itself from sibling tools by directing use when no dedicated tool covers the needed endpoint.

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?

The description gives explicit usage guidance: use when no dedicated tool covers the need, then follow up with calagopus_get. This directly addresses when to use the tool relative to alternatives.

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

Deploy Server