Skip to main content
Glama
WYRE-AI

QuickBooks Online MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

qbo_payment_methods_search

Find QuickBooks Online payment methods by partial name match. Get matching records with optional pagination and result limits to control the search.

Instructions

Search PaymentMethod records by Name (LIKE match).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term matched against Name with LIKE '%term%'
maxResultsNoMaximum number of results to return (default: 100, max: 1000)
startPositionNoStarting position for pagination (1-based, default: 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description provides basic behavioral info (LIKE match on Name) but omits pagination behavior, sorting, case sensitivity, or rate limits. Adequate but minimal.

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?

Single sentence with 7 words, front-loads the purpose. No wasted words.

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

Completeness2/5

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

Lacks explanation of return values (no output schema), error behavior, or handling of no results. Incomplete for a search 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 100%; the description adds 'LIKE match' beyond the schema's '%term%' but offers limited additional meaning. Baseline 3.

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 ('Search') and resource ('PaymentMethod records'), and specifies the search method (by Name with LIKE match). Distinguishes from sibling search tools targeting different resources.

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?

No guidance on when to use this tool versus the sibling 'qbo_payment_methods_list' or other search tools. Does not mention use cases or exclusions.

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

Deploy Server

Other Tools