Skip to main content
Glama

Base Agent Due-Diligence Kit

Sage catalog (free)

defi_dossier_catalog
Read-onlyIdempotent

FREE. Free catalog of Sage Control Dossiers: covered protocols, contract addresses, prices, methodology.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 the genuinely useful behavioral fact that the call is free of charge (relevant against paid/x402 siblings), but says nothing about response shape, pagination, or how large the catalog is.

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 definition is short and front-loaded, but the 'FREE. Free catalog...' construction duplicates the same word pointlessly, spending a full sentence on information already conveyed. The remaining content is dense but the leading redundancy costs a point.

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-parameter catalog with no output schema, the description covers the essentials by naming the four kinds of content returned, which lets an agent decide whether to call it. It is only slightly incomplete in not clarifying whether the catalog is static or whether entries link to the individual dossier tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not misrepresent any inputs.

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 resource (a catalog of Sage Control Dossiers) and enumerates its contents (covered protocols, contract addresses, prices, methodology), so an agent can infer this is a discovery/listing tool. It never states an action verb (list/retrieve) and does not distinguish itself from defi_control_dossier or defi_dossier_preview, so it falls 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 Guidelines2/5

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

The only usage signal is the repeated 'FREE', which hints there is no payment or x402 preflight involved, but it does not say when to call this versus fetching a specific dossier or running a preview. No prerequisites, exclusions, or alternative routing are given.

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