Skip to main content
Glama

Base Agent Due-Diligence Kit

Sage Research #1 — Who Can Move Your Money? ($0.100)

defi_research_report
Read-onlyIdempotent

Sage Research #1 (2026-11), long-form markdown: "Who Can Move Your Money?" Control and governance due diligence on Morpho Blue, Aerodrome and Moonwell (Base), the Governance Attack Cost framework, and a pre-deposit DeFi checklist. PAID: $0.100 per call in USDC on Base via x402, or use a 0.25 USDC transfer pass (pay_tx). See payment_options. By Sage.

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": "defi_research_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNomarkdown (default): the whole report as one markdown string. sections: an array of {title, markdown}, one per chapter (summary, Morpho Blue, Aerodrome, Moonwell, pre-deposit checklist, limitations, sources).
pay_txNoOptional, for the plain-transfer option (no x402 needed): hash of a USDC transfer of >= 0.25 USDC to this server's receiving address (get it from the payment_options tool). One transfer unlocks every paid tool for 24h.
pay_chainNoChain of pay_tx (default: inferred; 0x hash = base, base58 signature = solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, so the bar is lower, and the description adds genuinely non-obvious behavior: a per-call price, the alternative transfer-pass mechanism, and the fact that one transfer unlocks every paid tool for 24 hours. It doesn't state what happens on an unpaid call (e.g. a 402 response shape), which keeps it from a 5.

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?

Two sentences, front-loaded with the report identity and contents before payment terms. Information-dense but every clause carries content; the only minor redundancy is repeating the $0.100 price alongside the title's price tag.

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

Completeness4/5

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

For a zero-required-parameter read tool with a fully documented schema, the description covers identity, contents, output format, and payment mechanics, and defers the payment address to payment_options. The main residual gap is the failure mode when payment is absent or invalid, which matters for a paid endpoint.

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 description coverage is 100% and the schema already spells out format (markdown vs sections, with the chapter list), pay_tx, and pay_chain inference. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 names a specific deliverable (a long-form markdown report, 'Who Can Move Your Money?') and enumerates its contents: governance due diligence on Morpho Blue, Aerodrome and Moonwell, the Governance Attack Cost framework, and a pre-deposit checklist. An agent can tell exactly what it retrieves. It stops short of distinguishing itself from the related dossier/attack-cost siblings, which is why it isn't a 5.

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?

It explicitly lays out the two access paths — $0.100 per call via x402, or a 0.25 USDC transfer pass validated through pay_tx — and routes the agent to payment_options for the receiving address. What's absent is positional guidance relative to siblings (e.g. when to use this full report versus defi_dossier_preview or governance_attack_cost).

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