Fetch recent errors for a SingleStore pipeline and database to troubleshoot data loading failures and monitor pipeline health.
Most recent errors for one pipeline, for the Pipeline Monitor app.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| database | Yes | ||
| pipeline_name | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint=true annotation already establishes this is a safe read. The description adds ordering ('most recent') and scope ('one pipeline'), but says nothing about rate limits, what error fields are returned, or how the limit interacts with ordering — useful context that is missing.
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?
A single short, front-loaded sentence with no filler. It is efficient, though the terseness contributes to the gaps in other dimensions rather than being purely a virtue.
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 output schema, 0% parameter documentation, and only a readOnly annotation, the description is too thin for a tool that requires two identifiers and exposes a limit. It omits return shape, identifier semantics, and limit behavior.
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?
Schema description coverage is 0%, so the description carries the full burden and adds essentially nothing about the three parameters. It does not explain that pipeline_name and database are required, nor what limit controls (default 25), nor the relationship between the two required identifiers.
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?
The description states a clear verb+resource: retrieving the most recent errors for a single pipeline. An agent can tell this returns error data, but it never distinguishes itself from closely related siblings like pipeline_monitor_data or pipeline_status, leaving some ambiguity about which to pick.
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?
There is no guidance on when to use this versus pipeline_monitor, pipeline_monitor_data, pipeline_status, or test_pipeline. 'For the Pipeline Monitor app' is context about the domain, not a usage condition or exclusion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.