Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

defi_tvl

[object Object]

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": {
      "DeFi TVL - total value locked for any protocol": "<DeFi TVL - total value locked for any protocol>"
    },
    "name": "defi_tvl"
  }
}

Input Schema

NameRequiredDescriptionDefault
DeFi TVL - total value locked for any protocolYesParameter: DeFi TVL - total value locked for any protocol
defi tvl,total value locked,protocol tvl,defi,tvl,protocol rankingNoParameter: defi tvl,total value locked,protocol tvl,defi,tvl,protocol ranking
Total value locked in USD for any DeFi protocol slug (aave, lido, uniswap, eigenlayer...), plus chains, category and links. Call with no protocol to get the 25 largest protocols ranked by TVL. Source: DefiLlama.NoParameter: Total value locked in USD for any DeFi protocol slug (aave, lido, uniswap, eigenlayer...), plus chains, category and links. Call with no protocol to get the 25 largest protocols ranked by TVL. Source: DefiLlama.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses nothing — not the data source, freshness, units, nor whether the call is read-only. A mutation-versus-read distinction, result size expectations, and failure modes are all absent.

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

Conciseness1/5

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

The body is a single stringified-object artifact with no front-loaded statement of purpose and nothing that earns its place. This is under-specification or outright breakage, not conciseness.

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

Completeness1/5

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

For a tool with three parameters, one required, no annotations, and no output schema, the description must do heavy lifting. Instead it is entirely empty of usable content, leaving the agent with no basis to invoke the tool correctly.

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 reported at 100%, which establishes a baseline of 3 regardless of the description's silence. However, the schema "descriptions" are just restatements of the tool blurb rather than genuine per-parameter semantics, so the description contributes zero additional meaning on top of them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is the literal string "[object Object]", a serialization failure that communicates nothing about the tool's verb, resource, or scope. An agent cannot distinguish defi_tvl from any sibling such as token_price or get_crypto_prices using this text.

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

Usage Guidelines1/5

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

No when-to-use, when-not-to-use, or alternative-selection guidance appears in the description at all. Any hint about calling it with no protocol to get the top 25 by TVL lives only inside a schema property name, not in the description field an agent reads first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GadgetHumans API Hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources