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 | [] |
Procfy
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 indicate idempotent=true, readOnlyHint=false, destructiveHint=false. The description adds that the conversation array should contain recent messages for reproduction, which is useful behavioral context. However, it does not elaborate on other behavioral aspects like response behavior or side effects.
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 a single, concise sentence with no unnecessary words. It is front-loaded and easy to read.
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?
Given no output schema and the tool's purpose (reporting), the description provides enough context for the agent to understand what to do and include. It does not explain return values, but that is acceptable for such a 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?
Schema coverage is 0%, so description must compensate. It specifies that the 'conversation' parameter should include recent messages, adding meaning. The 'message' parameter is implied to be the bug report, and 'context' is not explained. Partial coverage.
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 tool's purpose: 'Report a bug, missing feature, or send feedback.' It is specific and distinguishes from sibling tools which are mostly procfy-related or authentication tools.
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 instructs to 'Include the conversation array with recent messages for reproduction,' guiding when to use the tool. It does not explicitly state when not to use it or mention alternatives, but the guidance is clear enough.
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
Disambiguation4/5
Most tools have clear, distinct purposes, especially the procfy_list_* tools which each target a different entity. The platform tools (authenticate, connect, marketplace) are also distinguishable. However, the marketplace tool is multi-purpose with different actions, which could cause some confusion, but descriptions help.
Naming Consistency3/5
Procfy-specific tools follow a consistent 'procfy_verb_noun' pattern, but platform tools (authenticate, connect, marketplace, etc.) lack a prefix and mix verb and noun forms (e.g., marketplace is a noun). This inconsistency in naming conventions across the set reduces clarity.
Tool Count4/5
With 16 tools, it's slightly above the ideal 3-15 range, but still reasonable for a domain covering multiple entities (accounts, bank accounts, categories, etc.). The inclusion of platform tools (6) contributes to the count, but they are necessary for the server's operation.
Completeness2/5
The server provides extensive list operations and a create for transactions, but lacks update/delete for transactions and CRUD for other entities (categories, contacts, etc.). No tool for getting individual entities (except transaction and bank account balance) or creating/modifying them. Significant gaps for a full lifecycle.