Skip to main content
Glama

BRAINIAC DeFi Intelligence

Search DeFi protocols

defi-intelligence_protocols_search

Search DeFi protocols by name, symbol, description, category, or chain using the DeFiLlama public API. Filtering is performed client-side. Price $0.05 USDC. POST /api/v1/defi-intelligence/protocols/search. Unpaid calls return 402 and do not run.

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

Input Schema

NameRequiredDescriptionDefault
chainNo
limitNo
queryNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does a lot: it discloses the data source (DeFiLlama public API), that filtering is client-side (so results may be a broad fetch narrowed locally), the per-call price of $0.05 USDC, the POST endpoint, and that unpaid calls return 402 without running. The main gap is no guidance on result volume or pagination behavior for such a broad listing.

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?

Compact and well front-loaded: purpose first, then searchable fields, then operational details (client-side filtering, price, endpoint, 402 behavior). Every sentence carries information. The endpoint path is the least useful line to an agent but is a minor cost.

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

Completeness3/5

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

For a 4-parameter, zero-required search tool with no output schema and no annotations, the description is adequate on operations (price, auth failure) but thin on the things an agent most needs: how the parameters interact and whether a broad no-query call is even sensible. A note on unpaginated vs limited result behavior would close the gap.

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 0%, so the description must compensate, and it partially does by naming the searchable facets (name, symbol, description, category, chain). But it doesn't map these to the four actual parameters (query, chain, category, limit), nor explain that limit defaults to 100 with a 1000 maximum or that query and the facet filters combine with AND logic. Semantics for 'query' vs 'category' vs 'chain' remain ambiguous.

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 (search) and resource (DeFi protocols) plus the searchable fields (name, symbol, description, category, chain), so it's clearly distinguishable from siblings like protocols_profile or protocols_tvl_current. It doesn't explicitly name a sibling to route away from, which keeps it just shy of 5.

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

Usage Guidelines3/5

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

Usage is implied by the searchable fields and the note that filtering happens client-side, but there's no explicit when-to-use vs when-not guidance, and no mention of when protocols_profile or chains_tvl would be the better pick. An agent can infer the lookup use case but gets no exclusions.

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