GET https://ticks.bnm.farm/mariners-d8 — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. USCG D8 / Gulf LNM Unpaid returns HTTP 402. After a valid X-PAYMENT, the same URL returns JSON. Not a new SKU.
| Name | Required | Description | Default |
|---|---|---|---|
| x_payment | No | Optional x402 X-PAYMENT value forwarded to the paid GET as the X-PAYMENT header. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does well: it states the payment amount, recipient address, the unpaid 402 response, and the JSON success response. It does not detail rate limits or payload structure, but the essential paid-GET behavior is transparent.
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 key facts are packed compactly and the URL is front-loaded, but the description is telegraphic and the final phrase 'Not a new SKU.' is cryptic and does not clearly earn its place. It could be clearer without losing conciseness.
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 one-optional-parameter paid endpoint with no output schema and no annotations, this description covers the essential operational context: URL, price, payee, failure mode, success format, and the X-PAYMENT precondition. The remaining gaps, such as how to obtain a valid payment token and JSON field details, are mino.
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 input schema already fully documents x_payment as an optional x402 value forwarded as the X-PAYMENT header, giving 100% schema coverage. The description's mention of 'a valid X-PAYMENT' adds no meaningful parameter-level detail beyond that baseline.
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 identifies the action as a GET to a specific paid endpoint for 'USCG D8 / Gulf LNM', with explicit cost and recipient. It distinguishes the resource enough from the many mariners-style siblings, though it does not explicitly compare them.
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 resource name and payment flow imply when this tool should be used, and the 402 behavior sets an expectation for unpaid calls. However, there is no explicit guidance on when to choose this over mariners-d7, mariners-d11, or other related mariners tools.
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.
Most tools map cleanly to distinct regulatory document collections (FDA, EPA, FDIC, etc.), so the majority are unambiguous. However, 'search' and 'firm-check' both offer free search with overlapping scope, and 'get-one' vs 'get-page' are easily confused payment operations. Similar prefixed names like mariners, mariners-d7/d8/d11 and gmp/gmp-md add further boundary fuzziness.
The bulk of tools follow a consistent lowercase-hyphenated source-slug convention (aaib-reports, cder-reviews, cfpb-orders), which is predictable. But utility tools break the pattern with imperative/descriptive names (search, firm-check, get-one, get-page), and 'ticks' is a bare noun that doesn't fit either style. The mixed conventions are readable but not uniform.
At 46 tools, this is a heavy surface that will be unwieldy for an agent to navigate and select from. Each tool does represent a distinct data product, but the sheer volume exceeds what earns its place in a coherent MCP tool set. A door-based catalog design might work better with a smaller number of parameterized tools.
The core workflow is well covered: per-door search, cross-door search, single-document retrieval via ?id=, paginated page retrieval, and payment handling are all present. Minor gaps exist, such as no tool to enumerate all available doors/catalogs or inspect schemas, and firm-check returns only citations rather than bodies. Overall it's a complete access lifecycle for the data-shop domain.