Skip to main content
Glama

quickbooks_list_credit_memos

Retrieve credit memos from QuickBooks to track customer credits and manage refunds.

Instructions

Quickbooks connector operation list_credit_memos (platform tool quickbooks.list_credit_memos).

Routes through /api/tools/invoke under your JWT, tenant, and company scope.

Args: arguments: JSON string of arguments for the connector operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo{}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The description mentions routing through an endpoint under JWT/tenant/company scope but does not disclose behavioral traits such as read-only nature, idempotency, or side effects. Since no annotations are provided, the description should offer more behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise but contains redundancy (e.g., 'Quickbooks connector operation ... (platform tool ...)'). It lacks a clear structure with sections or bullet points.

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?

Despite having an output schema, the description does not explain what the tool returns or what valid arguments are. Given the tool's complexity and the context signals, the description is incomplete.

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

Parameters1/5

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

The only parameter, 'arguments', is described as a 'JSON string of arguments for the connector operation', which adds no semantic value beyond the input schema. With 0% schema description coverage, the description fails to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it lists credit memos, matching the tool name. However, it does not clarify what a credit memo is or distinguish this tool from other QuickBooks list tools like quickbooks_list_invoices or quickbooks_list_bills. The purpose is clear but lacks differentiation.

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

Usage Guidelines1/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. There is no mention of prerequisites, context, or typical use cases.

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/RPasquale/lightbulb-mcp'

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