Retrieve the built-in default pipeline configuration (virtual template, id=0) to review PoisonDash's default hyperparameters before creating a saved configuration.
Get the built-in default pipeline configuration (id=0, a virtual template, not a saved row). Use this to see PoisonDash's default hyperparameters before creating a real configuration.
| 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 readOnlyHint and idempotentHint, so the description's added value is the key trait that this returns a virtual template with no backing row, meaning no persistence and stable output. It could go slightly further on the return shape, but the essential behavioral distinction is disclosed.
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: identity/mechanics first (id=0, virtual template, not a saved row), then the purpose (see defaults before creating a real configuration). No filler.
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?
With no parameters, no output schema, and annotations covering the safety profile, the description supplies what an agent needs to decide to call it and what to expect conceptually (default hyperparameters). A brief note on the response contents would make it fully complete.
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 there is nothing for the description to document and the baseline of 4 applies.
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 and resource ('get the built-in default pipeline configuration') and disambiguates from the sibling get_configuration/list_configurations by explaining it is id=0, a virtual template rather than a saved row.
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?
Explicitly says when to use it: to inspect PoisonDash's default hyperparameters before creating a real configuration, which implicitly steers the agent to create_configuration for persistence. It does not spell out a 'when not to use' case, but the contrast with saved configurations is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.