get_payment_typesRetrieve all available payment types such as credit card, check, or cash to specify the payment_type field when creating jobs, customers, or estimates.
List all available payment types (e.g., credit card, check, cash). Use these values for the payment_type field on create_job, create_customer, or create_estimate. Cached 30 minutes.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds a useful behavioral detail beyond annotations: results are cached for 30 minutes, which warns the agent that values may be slightly stale.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler: it states the purpose, gives examples, explains downstream usage, and notes the cache duration. Every sentence earns its place and the most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter, read-only reference-list tool, the description is fully sufficient: it identifies what is returned, how to use it, and the caching behavior. No output schema exists, but for this simple list, the return value is self-evident.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the description carries no parameter burden. Per the baseline for tools without parameters, this is appropriate, and the description still explains how the returned values should be used.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'List' with the resource 'payment types' and includes concrete examples. This clearly distinguishes it from the entity-focused sibling tools like get_job_categories or get_job_statuses.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly explains when to use this tool: to obtain values for the payment_type field on create_job, create_customer, or create_estimate. It does not discuss exclusions or alternatives, but the usage context is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.