Skip to main content
Glama

Quickbooks

by io.github.pipeworx-io

Send Pipeworx Feedback

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a claim_token; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNobug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
contextNoOptional structured context: which tool, pack, or vertical this relates to.
messageNoYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_tokenNoRead the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / claim_token
      Added value: +{
+  "description": "Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "type",
-  "message"
-]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Discloses several non-obvious behaviors beyond the neutral annotations: rate-limited to 5 per identifier per day, does not count against tool-call quota, filing without an account returns a claim_token, and the token can be used later to check status. Also warns not to paste the end-user's prompt. This is thorough behavioral disclosure.

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 one well-organized paragraph with a clear first sentence and logical progression from purpose to constraints. While longer than strictly minimal, every sentence contributes meaningful detail (e.g., rate limits, token usage, source scoping). It could be tightened slightly but is appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description fully explains expected behavior: what happens when filing with no account (returns claim_token), how to retrieve status later, daily rate limits, and quota impact. It covers all relevant scenarios for a feedback tool with four optional parameters, making it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description adds workflow context not in the schema, such as explaining the claim_token round-trip and emphasizing the need for tool-specific context. This extra value lifts it above baseline but doesn't reinvent parameter documentation.

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 opens with a clear, specific statement: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It enumerates the exact types of feedback (bug, feature, data_gap, praise) and explicitly distinguishes from siblings by scoping only to Pipeworx tools and instructing to file elsewhere for other MCP servers.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: 'Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog...' Also gives a strong exclusion: 'if the tool came from a different MCP server... file it with that server instead.' This clearly prevents misuse and directs to alternatives.

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

All Quickbooks toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Several tools are near-duplicates (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), and there are overlapping clusters among the polymarket_* tools, research tools (deep_research, entity_profile, compare_entities, recent_changes), and AI-visibility tools (ai_visibility_check vs scan_competitor_ai_presence). The detailed descriptions help, but an agent selecting among these could easily pick the wrong one.

Naming Consistency2/5

Snake_case is used consistently, but the naming pattern is otherwise mixed: some tools are verb_noun (validate_claim, suggest_questions), some are bare nouns (entity_profile, polymarket_edges), some are verbs without objects (remember, forget, ask_pipeworx), and only the five QuickBooks tools share a qb_ prefix. This creates multiple naming ecosystems with no unified convention.

Tool Count2/5

At 36 tools, this is well above the 25+ threshold for 'too many'. More importantly, the server is named Quickbooks but only 5 tools are accounting-related; the other 31 are unrelated Pipeworx data, prediction-market, memory, and meta tools, making the count both excessive and off-purpose.

Completeness2/5

For the QuickBooks domain named by the server, the surface is read-only: get customer, get invoice, list accounts, list invoices, and generic query. There are no create, update, delete, payment, bill, deposit, or report operations, which is a significant gap. For the broader Pipeworx data domain it is fairly complete, but that domain is not what the server name promises.

Resources