Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

protocol_health_list_protocols

Read-onlyIdempotent

[Protocol Health Oracle] All tracked protocols with their latest health score and verdict.

Use when you need every tracked protocol with its latest score and verdict. Not for one protocol's details (use protocol_health_score).

Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

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": "protocol_health_list_protocols"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. Rows to return (default 100, max 2000).
offsetNoOptional. Pagination offset (default 0).
min_tvlNoOptional. Only protocols with TVL >= this USD amount.
categoryNoOptional. Filter by DefiLlama category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so safety is free; the description adds the non-obvious payment behavior that no structured field carries — x402 USDC-on-Base pricing, the API-key bypass, and the crucial clarification that an HTTP 402 carries a decoded price quote and is 'not a failure'. That prevents an agent from misreading a paywall response as an error.

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?

Scope is front-loaded and the payment caveat is placed last where it belongs. The second sentence largely restates the first ('every tracked protocol with its latest score and verdict' vs 'All tracked protocols with their latest health score and verdict'), which is mild waste in an otherwise tight three-sentence definition.

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 read-only list endpoint with fully covered parameters and no output schema, the description covers purpose, routing, and the paywall edge case. It stops short of describing the shape of a returned row (score, verdict fields) or default page size behavior in prose, but the schema's defaults cover the latter.

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 limit, offset, min_tvl, and category are fully documented in the schema. The description adds nothing about filtering or pagination semantics, so the baseline 3 applies rather than a higher score.

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

Purpose5/5

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

Opens with a specific resource and scope: 'All tracked protocols with their latest health score and verdict.' The bracketed oracle tag plus the explicit sibling callout ('Not for one protocol's details') lets an agent distinguish this from protocol_health_score without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use when you need every tracked protocol with its latest score and verdict') and an explicit exclusion routing to the correct alternative ('Not for one protocol's details (use protocol_health_score)'). Nothing is left to inference.

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

All Wicked MCP 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