Skip to main content
Glama
chrischall

honeybook-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_payment_methods

Read-only

Retrieve saved payment methods for a client account with a vendor, including card type, brand, last four digits, expiry, and default status. Returns an empty array when none are saved.

Instructions

List saved payment methods for your client account with a vendor: id, type, brand, last 4, expiry and whether it is the default. Empty array if none are saved. view="raw" returns the untrimmed records (billing name/address and Stripe references).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "raw" returns the upstream payload unprojected. compact returns only the card-on-file fields; "raw" returns the untrimmed records, including billing name/address and Stripe references.
originNoPortal origin (e.g. https://<vendor>.hbportal.co). Optional when only one session is active.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"raw\" returns the upstream payload unprojected. compact returns only the card-on-file fields; \"raw\" returns the untrimmed records, including billing name/address and Stripe references.",
+  "enum": [
+    "compact",
+    "raw"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful behavior: returns an empty array when no methods are saved, and view='raw' yields untrimmed records including billing name/address and Stripe references. This goes beyond the structured annotation.

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?

Two sentences, front-loaded with the resource and field list; the empty-array behavior is a worthwhile addition. The raw-view clause is slightly redundant with the schema's parameter description but does not bloat the text.

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

Completeness4/5

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

The description is adequate for a simple read-only listing: it names returned fields, defines the empty case, and summarizes the raw variant. With no output schema, a bit more detail on the raw record shape could help, but the schema covers the two parameters and annotations cover safety.

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 description coverage is 100%, so the schema fully documents both view and origin. The description's mention of view='raw' repeats what the schema already says, adding no new parameter-level meaning; baseline 3 is appropriate.

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 specific verb and resource ('List saved payment methods') and enumerates the exact fields returned (id, type, brand, last 4, expiry, default). This makes it easy to distinguish from sibling list_payments, which would concern transactions rather than saved card-on-file data.

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

Usage Guidelines3/5

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

The intended use is implied by the resource name and field list ('saved payment methods for your client account with a vendor'), so an agent can infer when to call it. However, it does not explicitly state when not to use it or mention alternatives such as list_payments or pay_invoice.

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