Skip to main content
Glama

BRAINIAC DeFi Intelligence

Get protocol information

defi-intelligence_protocols_profile

Retrieve detailed information for a specific DeFi protocol by ID or slug from DeFiLlama public API. Price $0.02 USDC. POST /api/v1/defi-intelligence/protocols/profile. Unpaid calls return 402 and do not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "defi-intelligence_protocols_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

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?

With no annotations, the description carries the full burden and does disclose genuinely useful behavior: per-call cost of $0.02 USDC, the POST endpoint, and that unpaid calls return 402 without executing. It stops short of explaining not-found behavior, whether failed lookups are billed, or what the response contains.

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 tight sentences, front-loaded with the purpose before the commercial and failure-mode details. The endpoint path and price are not filler for a paid API — each sentence carries information an agent needs before calling.

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 single-parameter lookup with no output schema, the definition covers what to supply, what it costs, and how unpaid calls fail. The main gap is the absence of any sense of what 'detailed information' comprises, which matters since no output schema documents the return shape.

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?

Schema coverage is 0% and the schema merely types 'id' as a bounded string. The description compensates meaningfully by stating the parameter accepts either a protocol ID or a slug, which the schema alone would never reveal, though it gives no format examples for either form.

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 verb and resource: 'Retrieve detailed information for a specific DeFi protocol by ID or slug'. The 'by ID or slug' scoping implicitly separates it from the sibling search tool, though it never names that alternative. 'Detailed information' remains vague about what fields are actually returned.

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 only implied: the agent must already possess an id or slug, which hints that free-text lookup belongs in defi-intelligence_protocols_search. There is no explicit when-to-use, when-not-to-use, or named alternative, and no guidance on what to do if the identifier is unknown.

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