Retrieve an overview of all configured Flink clusters in one call; unreachable clusters are reported as errors without failing the entire request.
Overview of every configured cluster in one call; unreachable clusters are reported with an error instead of failing the whole call.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent and non-destructive. The description adds genuinely new behavior: partial-failure semantics, where an unreachable cluster yields an error rather than aborting the whole call — the most important trait for a fan-out tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with the scope front-loaded and the failure-handling caveat second. Nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and the description covers the one non-obvious runtime behavior (per-cluster error isolation). Only the relationship to the single-cluster sibling is left unstated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4; the description correctly makes no parameter claims and needs none.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource: an overview of every configured cluster in a single call. The phrase 'every configured cluster' implicitly distinguishes it from the single-cluster sibling cluster_overview, though that sibling is never named.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'In one call' hints that this is the aggregation choice over per-cluster calls, but no explicit when-to-use or when-not guidance is given, and no alternative sibling (cluster_overview, list_clusters) is named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.