camelotwebtools-mcp

camelot_bug_report_template

Idempotent

Create structured bug reports with severity, reproduction steps, environment details, and observed vs expected behavior. Helps teams document reproducible defects clearly for efficient tracking.

Instructions

Bug Report Template: Format clear, reproducible bug reports with steps, environment details, and logs.. Local browser processing. Canonical URL: https://www.camelotwebtools.com/tools/bug-report-template

Input Schema

TableJSON Schema

Name	Required	Description	Default
`severity`	No	Bug severity level (critical, high, medium, low)	high
`issueTitle`	No	Concise summary title of defect or bug	Memory leak in worker pool during heavy PDF assembly
`actualBehavior`	No	Actual observed behavior or error encountered
`expectedBehavior`	No	Expected correct system behavior
`stepsToReproduce`	No	Ordered step-by-step reproduction instructions
`environmentDetails`	No	OS, browser version, device, or runtime environment details

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Execution status of the tool (success or error)
`prefillUrl`	Yes	Direct deep-link URL to view, edit, and export in Camelot Web Tools
`canonicalUrl`	Yes	Canonical web URL for this tool on camelotwebtools.com
`documentTitle`	Yes	Title of the generated document, report, or calculation output
`documentMarkdown`	Yes	Complete structured output and body formatted in clean Markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 16, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate the tool is idempotent and non-destructive. The description adds 'Local browser processing,' which is useful privacy/execution context, but it does not disclose return behavior, file generation, or how logs are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the core purpose. The redundant canonical URL and the double period after 'logs' slightly reduce polish, but overall the text is efficient.

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?

All six parameters are fully described in the schema, no parameters are required, and an output schema exists. The description provides enough context to invoke the tool successfully, though usage guidance is absent.

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 description coverage is 100%, so the parameters are already fully documented. The description's mention of steps, environment details, and logs loosely maps to schema fields, but does not add meaningful detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states that the tool formats bug reports with steps, environment details, and logs, which clearly identifies the deliverable and differentiates it from the many sibling generators. It is slightly vague on exact output form, but the verb and resource are clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool versus the numerous sibling template/generator tools. The description does not mention preconditions, alternatives, or exclusion criteria.

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

Deploy Server