Skip to main content
Glama

Buy DAO report

buy_dao_report
Read-onlyIdempotent

Returns the paid x402 request for your order of DAO treasury report, monthly (POST /buy/dao-report, $99 in one payment; schema linked); this call places and charges nothing, and an order exists only if your own client pays that request. POST that JSON body to the URL with an x402 or MPP client; the order id and status link come back with the receipt. Bad input is refused before any charge. Paying the request charges at once and skips the free check; the free check is a separate, optional call: POST the same body plus your email to /buy/dao-report/check (email required there). If not delivered as described: full refund on request (/refunds). Monthly plan: one report from public on-chain data within 24 hours of payment, no automatic billing; for a year use buy_dao_report_yearly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buy_dao_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNochain of the treasury address
emailNooptional: where to send the files too; without it they are on the order status page
spaceNoyour Snapshot space id, e.g. yourdao.eth
addressNooptional treasury address if you have no Snapshot space

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added

TDQS

A4.3/5.0
Behavior5/5

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

The description goes well beyond the annotations by explaining the two-step payment flow: the call itself charges nothing and no order exists until the client pays the returned request. It adds refund terms (/refunds), the 24-hour delivery window, and the no-auto-billing character of the plan. This resolves the apparent tension between readOnlyHint=true and a paid product, with no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, and every sentence carries real content such as price, refunds, and delivery SLA. The prose is a dense run-on chain of semicolon-linked clauses, however, and repeats the charge behavior across two separate statements, which makes it harder to scan than necessary.

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?

For a payment-flow tool with no output schema, the description supplies everything an agent needs: what is returned, what the client must do next, where the order id and status link come from, refund terms, and the delivery SLA. Nothing material is left to inference.

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%, so chain, space, address, and email are already documented, including the address-as-alternative-to-Snapshot-space relationship. The description's only added meaning is that email is mandatory on the separate /check endpoint, which is a minor contribution. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns the x402 payment request for a DAO treasury report on the monthly plan, with the exact endpoint and price. It distinguishes the monthly product from the yearly sibling buy_dao_report_yearly. The opening phrase "paid x402 request for your order" is slightly circular, but it is clarified within the same sentence.

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

Usage Guidelines5/5

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

It explicitly selects the tool for the monthly plan and routes yearly buyers to buy_dao_report_yearly. It also names the separate free-check endpoint /buy/dao-report/check and its condition (post the same body plus a required email), and states the prerequisite: an x402 or MPP client must pay the returned request.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources