Skip to main content
Glama
wyre-technology

QuickBooks Online MCP Server

qbo_vendors_create

Add a new vendor to QuickBooks Online with name, billing address, contact details, and 1099 tax information using required display name.

Instructions

Create a new Vendor record in QuickBooks Online.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
BillAddrNoBilling address object with Line1, City, CountrySubDivisionCode, PostalCode
GivenNameNoFirst name
FamilyNameNoLast name
Vendor1099NoWhether this vendor receives a 1099 at year end
CompanyNameNoCompany name
DisplayNameYesDisplay name for the vendor (required, must be unique)
PrimaryPhoneNoPrimary phone object, e.g. {"FreeFormNumber": "555-1234"}
TaxIdentifierNoTax ID (e.g. EIN or SSN) used for 1099 reporting
PrimaryEmailAddrNoPrimary email address object, e.g. {"Address": "vendor@example.com"}
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It only states 'Create' without explaining side effects, required permissions, uniqueness constraints, or error scenarios like duplicate DisplayName.

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?

A single, front-loaded sentence contains no fluff and immediately conveys the tool's purpose. It is appropriately concise.

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?

For a create tool with 9 parameters, including nested objects, and no output schema, the description lacks context on return values, error handling, uniqueness requirements, and how to structure nested fields. It is insufficient for an agent to use correctly.

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% with parameter descriptions, so the baseline is 3. The description adds no extra meaning beyond what the schema provides, such as implying that DisplayName must be unique.

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 ('Create'), resource ('Vendor record'), and system ('QuickBooks Online'), which is specific and distinct from sibling tools like qbo_vendors_get or qbo_vendors_update.

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 is provided on when to use this tool versus alternatives, such as updating an existing vendor or searching before creating. No when-not-to-use or prerequisite information is included.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/qbo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server