Skip to main content
Glama

Base Agent Due-Diligence Kit

Sage Control Dossier: DeFi protocol risk (admin keys, upgradeability, governance) ($0.010)

defi_control_dossier
Read-onlyIdempotent

DeFi protocol risk check before you deposit, swap or vote: who can upgrade, pause or redirect user funds (admin keys, multisig/emergency council, timelock, governance attack cost), what admins cannot do, incidents and declared unknowns. Covers Aero (Aerodrome + Velodrome merger), Morpho Blue and Moonwell on Base. Look up by contract address or protocol name. Every claim is sourced and confidence-tagged JSON. PAID: $0.010 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_control_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoDossier id (one of slug / protocol / address is needed)
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.
addressNoA contract address you are about to use (e.g. Morpho 0xBBBB...FFCb, AERO token, VotingEscrow). Not covered = HTTP 400, not charged
protocolNoProtocol name, e.g. aero, aerodrome, velodrome, morpho, moonwell
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?

Beyond the readOnly/idempotent/openWorld annotations, it discloses cost ($0.010 per call in USDC on Base via x402), a 24h unlock alternative, and the nature of the response (sourced, confidence-tagged claims with declared unknowns). Coverage limits are stated (Aero/Morpho/Moonwell on Base only). It omits failure/error behavior in the description proper (the 400-not-charged case lives in the schema), so not 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?

Front-loaded with the risk functions an agent cares about, then coverage, then payment mechanics. The first sentence is dense with nested parentheticals and the trailing 'By Sage.' is filler, but nearly every clause carries decision-relevant information.

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?

With no output schema, the description does the necessary work of characterizing the return (sourced, confidence-tagged JSON with incidents and declared unknowns) and fully explains the payment model. Coverage boundaries and lookup keys are explicit. Only error/pagination-style edge behavior is left to the schema.

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%, so the schema already documents slug, pay_tx, address, protocol and pay_chain in detail. The description adds only the high-level framing that lookup is by contract address or protocol name, which is a restatement rather than new semantic detail; baseline 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?

States a specific verb+resource (protocol risk check / control dossier) and enumerates exactly what it returns: upgrade/pause/redirect power, admin keys, multisig, timelock, governance attack cost, incidents, declared unknowns. It also names the covered protocols (Aero, Morpho Blue, Moonwell on Base) and lookup modes. It does not explicitly distinguish itself from sibling preview/catalog tools, so it stops short of 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?

Gives a clear use context ('before you deposit, swap or vote') and names the payment alternative (0.25 USDC transfer pass via pay_tx, see payment_options) rather than leaving the agent to guess. No explicit when-not-to-use or named sibling alternative such as defi_dossier_preview for free lookups, which keeps it at 4.

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