calagopus-mcp

List egg configurations

calagopus_list_egg_configurations

Read-only

List reusable egg configuration presets to locate shared startup, stop, and script blocks that eggs can inherit, making server configuration consistent.

Instructions

List reusable egg configuration presets (shared startup/stop/script blocks eggs can inherit).

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

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number.
`detail`	No	summary returns the useful fields only; full returns the panel's complete record, which can be very large (a single server is ~15 KB, an egg ~13 KB).	summary
`search`	No	Free-text filter applied by the panel across the record's searchable columns.
`per_page`	No	Records per page (max 100).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 8, 2026

TDQS

A4/5.0

Behavior4/5

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

The description states it is a list operation, which aligns with the readOnlyHint and destructiveHint annotations. It does not contradict the annotations, and the list behavior is clear enough; no additional side-effect warnings are needed.

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 a single, focused sentence with no unnecessary words or repetition. It immediately conveys the tool's purpose without bloat.

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?

The description gives enough context to identify the entity being listed, and the schema covers pagination and detail-level parameters. Since there is no output schema, a bit more detail about the returned records could help, but it is not essential for a simple list tool.

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 coverage is 100% with each parameter described, so the description does not need to repeat parameter details. The description adds no extra parameter semantics, keeping it at the baseline for full schema coverage.

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?

Clearly specifies the action ('List') and the resource ('reusable egg configuration presets'), and distinguishes them from plain eggs by noting these are shared startup/stop/script blocks that eggs can inherit.

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 explains what the tool returns but does not explicitly say when to prefer it over sibling tools like calagopus_list_eggs or calagopus_get_egg. The distinction is inferable from the wording but not directly stated.

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

Deploy Server