List checks.
| Name | Required | Description | Default |
|---|---|---|---|
| asset | No | Filter by asset code. | |
| count | No | Page size (default 100). | |
| offset | No | Skip this many. | |
| status | No | active | activated. | |
| check_ids | No | Comma-separated ids. |
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?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds no further behavioral details such as pagination defaults, result ordering, or how the filter parameters combine.
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 and front-loaded, but the brevity borders on under-specification. It wastes no words, yet it omits all usage context and resource clarification.
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 five-parameter list operation with no output schema and an ambiguous resource name, a two-word description is insufficient. Sibling tools like getInvoices and getStats show the need for disambiguation, which this description does not provide.
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%, so the schema already documents all five parameters. The description adds no parameter-level meaning, but it does not need to since the schema carries that burden.
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 states a clear verb and resource ('List checks'), so an agent knows this is a read operation over check records. However, it provides no context about what a 'check' is and does not distinguish it from sibling list tools like getInvoices or getTransfers.
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?
There is no guidance on when to use getChecks instead of alternatives, no mention of prerequisites, and no typical use cases. The agent is left to infer the tool's role from its name alone.
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 maps to a distinct resource or action: invoices, subscription plans, subscriptions, checks, transfers, balance, rates, and auth flows. The two-step connect/connect_status pair is clearly separated into initiate and poll, and similar actions like archiveSubscriptionPlan versus cancelSubscription are explicitly differentiated.
The vast majority of tools follow a camelCase verb_noun pattern such as createInvoice, getSubscriptions, and refundInvoice. The exceptions are connect_status and get_docs, which use snake_case, creating a minor but noticeable inconsistency.
At 21 tools, the server is on the heavier side but the breadth of a merchant payment API justifies it: auth, invoices, subscriptions, transfers/checks, balances, exchange rates, stats, webhooks, and docs all need coverage. No tools feel redundant, though a few list-only endpoints could arguably be consolidated.
Core invoice and subscription lifecycles are well covered: create, list, delete, archive, cancel, and refund. However, there is no visible createTransfer or createCheck tool even though the API includes transfers/checks docs and deleteCheck/getTransfers, leaving a notable dead end for initiating transfers.