laen

army_list_services

FREE. List the LedgerProof Settlement Army's 21 live data services an agent can buy per-call with x402 (USDC on Base, no account, no subscription, no signup). Each entry returns its price in USD, the exact resource URL to call, and the PUBLISHED ACCEPTANCE RULE that must hold before payment is captured — settlement is proof-gated, so a deliverable that fails its own test is never charged for. Covers live web search and page extraction, prediction-market odds priced across Polymarket AND Kalshi with the cross-venue spread, FX and technical indicators, SEC filings, FDA recalls, CVE lookups, sanctions screening, DNS/RDAP, GLEIF LEI, Wikidata, Federal Register, World Bank indicators, weather, GitHub repo facts, and hash anchoring/verification. Call this first to see what exists and what it costs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	optional substring filter over service id and description (e.g. 'prediction', 'search', 'sanctions')
`max_price_usd`	No	optional: only return services at or below this price

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses key behavioral traits: the tool is FREE, settlement is proof-gated, and failed deliverables are never charged, which are important for agent decision-making.

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?

The description is a long single paragraph but each sentence adds substantive value. It front-loads 'FREE' and the core purpose, making it scannable despite its length. It could be broken into lists but remains efficient.

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

Completeness5/5

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

The description thoroughly explains what the tool returns (price, URL, acceptance rule), the x402 business model, and the breadth of data domains. With no output schema, this level of detail is complete and actionable.

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 coverage is 100% with both parameters described, so the schema already handles parameter semantics. The description does not add new meaning beyond the optional filters mentioned; it stays at baseline 3.

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 clearly states the tool lists the LedgerProof Settlement Army's 21 live data services and their costs, with a specific resource and scope. It explicitly distinguishes itself from siblings like army_buy and army_quote by positioning as a catalog/discovery tool.

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

Usage Guidelines4/5

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

The description gives explicit usage guidance with 'Call this first to see what exists and what it costs,' indicating when to use it. It does not mention when not to use or alternatives, but the purpose is obvious enough to imply it's the prerequisite before purchasing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All laen tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

The tools are mostly distinct: army_list_services and army_quote are clear (list vs. quote), and laen_find_blockers and laen_quote are similar but one finds blockers and the other quotes a specific blocker. However, army_quote and laen_quote both serve the purpose of providing payment requirements for their respective domains, and a agent might confuse which quote applies to which service. The distinction is reinforced by naming (army_ vs laen_) but still a minor overlap.

Naming Consistency3/5

The naming uses a mix of snake_case for verbs like 'army_buy' and 'army_list_services', but 'laen_find_blockers' and 'laen_resolve' follow a similar pattern. However, 'army_' and 'laen_' prefixes are inconsistent - one uses 'army' and the other 'laen', and the verbs are not consistently placed (buy vs list_services vs find_blockers vs resolve). The pattern is readable but not fully uniform.

Tool Count5/5

Six tools is appropriate for a server that spans two focused domains (Army services and LAEN blockers). Each tool has a clear role: list, quote, buy/resolve, and find, which is a tight functional set. This is well within the ideal range, and the server doesn't feel over- or under-loaded.

Completeness4/5

The server covers the full lifecycle for both domains: list services and find blockers (discovery), quote (pricing), and buy/resolve (payment and execution). The only gap is that there is no cancellation or refund tool, but given the fail-closed nature, that's not critical. The core workflow of discover->quote->pay->receive is complete.

Resources

Need Help?