mercoa_list_entity_payment_methodsList an entity's payment methods (bank accounts, cards, check, etc.). GET /entity/{entityId}/paymentMethods.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter by payment method type (e.g. bankAccount, card, check). | |
| entityId | Yes | Entity ID or foreign ID. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation 'readOnlyHint: true' already indicates read-only behavior. The description adds no additional behavioral context such as permissions, rate limits, or side effects. It is consistent with annotations but does not provide further transparency beyond the schema and annotations.
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 extremely concise: one sentence plus the endpoint. Every part is functional with no wasted words. It is front-loaded with the core action and resource.
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?
No output schema exists, and the description does not explain the return structure, pagination, or error handling. For a simple list endpoint, it is minimally adequate but could be more complete. Given the context, it lacks detail compared to richer sibling tools.
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?
Schema coverage is 100%, with both parameters fully described in the input schema. The description adds minimal extra meaning, only providing example values for the 'type' parameter. It does not compensate beyond what the schema already offers.
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 clearly states 'List an entity's payment methods' with examples of types, and provides the endpoint. It specifies the verb (List) and resource (entity's payment methods), distinguishing it from the sibling tool 'mercoa_get_payment_method' which retrieves a single method.
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?
No explicit guidance on when to use this tool versus alternatives. The description implies it is for listing all payment methods for an entity, but does not mention filtering, pagination, or conditions for use. It is adequate but lacks explicit when/when-not instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource (entity, invoice, transaction, payment method, organization) and action (create, find, get, list, update, add). There is no ambiguity between tools.
All tools follow the consistent pattern 'mercoa_verb_noun' using snake_case. Verbs like create, find, get, list, update are used predictably.
With 17 tools covering entities, invoices, transactions, payment methods, and organization, the count is well-scoped for a financial platform. Each tool justifies its existence.
The toolset covers core CRUD and query operations for the main resources. Minor gaps exist such as missing delete operations for entities and invoices, but the surface is largely complete for typical workflows.