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 | [] |
SEMA MT: APF Rural
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, establishing the safety profile. The description adds the useful behavioral instruction to include the conversation array for reproduction. However, it does not disclose what happens after reporting (e.g., confirmation, transmission) beyond the 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?
The description is two short sentences, front-loaded with purpose and adding one practical instruction. Every word earns its place, with no redundancy or fluff.
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?
The tool is simple (3 string params, no output schema), and the description covers its core purpose and the non-obvious conversation parameter. Annotations handle safety. It lacks detail on parameter contents but is otherwise adequate for a reporting tool.
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?
With 0% schema description coverage, the description needed to compensate but only explains the 'conversation' parameter's purpose (for reproduction). It does not clarify the required 'message' parameter or the optional 'context' parameter. The purpose statement implicitly suggests content for message but leaves it to the agent.
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 explicitly states the tool reports a bug, missing feature, or feedback, which is a specific verb+resource. This clearly distinguishes it from sibling tools like authenticate, connect, and show_version, which serve different purposes.
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?
The description provides clear context for usage: to report bugs, missing features, or feedback. It also advises including the conversation array for reproduction, but it does not explicitly list exclusions or alternative tools. Given the sibling tools are thematically distinct, this is sufficient.
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
A3.7/5.0
Disambiguation5/5
Every tool has a clearly distinct purpose: authenticate handles credentials, connect checks status, marketplace searches/invokes MCPs, report_bug sends feedback, show_version displays version info, toolkit_info shows installed MCPs, and sema_mt_apf_consultar performs the actual domain query. There is no overlap or ambiguity between them.
Naming Consistency2/5
Tool names follow mixed conventions: some are plain verbs (authenticate, connect), some are nouns (marketplace, toolkit_info), some are verb-noun (report_bug, show_version), and one is in Portuguese with a domain prefix (sema_mt_apf_consultar). This inconsistency makes naming patterns unpredictable.
Tool Count4/5
Seven tools is a reasonable count for this server, but six of them are generic platform utilities (auth, connection, diagnostics, marketplace) while only one is domain-specific. The count is appropriate, though the balance feels slightly off given the server's stated purpose appears to be a specific APF Rural consultation.
Completeness4/5
The domain surface is a single consultation endpoint, which is fully covered by sema_mt_apf_consultar. There is no obvious missing CRUD operation because the domain is inherently read-only. However, the toolkit lacks any domain-specific history, batching, or additional query capabilities, which could be considered a minor gap if more granular interactions were expected.