Skip to main content
Glama

Base Agent Due-Diligence Kit

Sage dossier preview (free)

defi_dossier_preview
Read-onlyIdempotent

FREE. Free preview of a Sage Control Dossier (Aero/Aerodrome, Morpho Blue, Moonwell on Base): headline and risk scores. Full sourced dossier: defi_control_dossier.

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_dossier_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoDossier id
addressNoA covered contract address
protocolNoProtocol name, e.g. aero, morpho, moonwell

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value by disclosing that the output is deliberately truncated to headline and risk scores, and that it is free. It says nothing about latency, rate limits, or what happens with an unknown slug/address.

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

Conciseness5/5

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

Three short fragments, front-loaded with 'FREE' as the key differentiator, then scope, then the upsell pointer. Nothing is wasted and the most decision-relevant fact comes first.

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 preview tool with no output schema, it tells the agent what comes back (headline and risk scores) and where the rest lives. The main gap is identifier semantics for a tool with three all-optional params and no stated requirement.

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 slug, address and protocol are already documented, and the baseline is 3. The description does not explain that all three parameters are optional or how they interact (e.g., whether one identifier suffices or they must agree), so it adds no meaning beyond the schema.

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 the concrete artifact (a Sage Control Dossier preview), lists the covered protocols (Aero/Aerodrome, Morpho Blue, Moonwell on Base), and states the payload (headline and risk scores). It also distinguishes itself from the full-dossier sibling by name. It stops short of a clean verb, so the 'get/read' framing is inferred rather than stated.

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 gives a clear routing rule: this is the free preview, and the full sourced version lives at defi_control_dossier. It does not state exclusions or clarify when a caller should prefer defi_dossier_catalog or how to decide between preview and full beyond 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