report_bug
Idempotent
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | ||
| message | Yes | ||
| conversation | No | [] |
MPT PB: Certidão Negativa de Feitos
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare non-read-only, non-destructive, and idempotent. The description adds minimal behavioral info beyond the requirement to include conversation. No mention of side effects, responses, or error states, but bar is lowered by annotations.
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?
Two compact sentences with clear, actionable language. No fluff, and the key usage instruction (include conversation) is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 3-param tool with no output schemachers, the description covers the essentials but omits what happens after reporting, potential side effects, or any return values. It's adequate but not thorough.
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 0%, so the description must clarify parameters. It explicitly mentions 'conversation' and its purpose, and 'message' is implicitly the bug report content. However, 'context' is left unexplained, and no parameter format details are given.
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?
The description clearly states the action:
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit instruction to include the conversation array for reproduction, but doesn't specify when to use versus alternatives. However, since siblings are unrelated, the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation2/5
The tools have overlapping purposes (authenticate and connect both relate to authentication) and the descriptions are verbose and repetitive, making it hard to distinguish their roles. The domain-specific tool mpt_pb_cnf_consultar is buried among generic platform management tools, creating confusion about the server's core function.
Naming Consistency2/5
Tool names follow no consistent pattern: some are verbs (authenticate, connect), others are nouns (marketplace), some are snake_case (mpt_pb_cnf_consultar), and others are compound nouns (toolkit_info, report_bug). This mixed naming makes it difficult to predict tool behaviors.
Tool Count3/5
With 7 tools, the count is within a reasonable range, but the set includes a mix of generic platform utilities (report_bug, show_version, toolkit_info) that seem unrelated to the server's stated purpose of providing a certidão negativa, giving it a bloated and unfocused feel.
Completeness2/5
The server offers only a single domain-specific operation (mpt_pb_cnf_consultar) with no additional related features, leaving a minimal surface for its stated purpose. The presence of unrelated platform tools does not address the gap in domain coverage, making the tool set incomplete for a robust certidão service.