Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

protocol_health_track_protocol

[Protocol Health Oracle] Track a new protocol. Scored immediately from live GitHub + DeFiLlama data.

Use when a protocol you care about is not tracked yet and you want it scored from live GitHub and DefiLlama data. Not for reading an existing score.

Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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": {
      "name": "<name>",
      "github_repo": "<github_repo>",
      "defillama_slug": "<defillama_slug>"
    },
    "name": "protocol_health_track_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name, e.g. "Lido".
chainNoOptional. Default "ethereum".
github_repoYesowner/repo, e.g. lidofinance/core.
defillama_slugYesDeFiLlama protocol slug, e.g. lido.
treasury_addressNoOptional. On-chain treasury address to score (Etherscan balance).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description reinforces this with 'writes state upstream (not read-only)' and adds an auth requirement, but 'the credentials or wallet signature noted above where applicable' is vacuous – no credentials are documented anywhere, and nothing explains what happens if the protocol is already tracked despite the non-idempotent hint.

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?

Three short front-loaded segments: purpose, usage, behavior. The bracketed '[Protocol Health Oracle]' prefix is decorative overhead, but otherwise there is little waste.

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 5-parameter mutation with no output schema, the description conveys the immediate-scoring outcome but omits what the caller gets back, whether re-tracking an existing protocol errors or updates, and any rate/cost implications. Adequate but with clear gaps.

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 all five parameters are documented with examples in the schema itself. The description only gestures at two of them via 'GitHub + DeFiLlama data' and adds no format or default detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb and resource ('Track a new protocol') and the data sources used for scoring (GitHub + DeFiLlama). It also distinguishes itself from reading an existing score, though it does not name the sibling tool (protocol_health_score) explicitly.

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

Usage Guidelines4/5

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

'Use when a protocol you care about is not tracked yet' gives a clear positive condition, and 'Not for reading an existing score' gives an exclusion. The exclusion implies the sibling to use but never names it, so the routing is slightly less crisp than it could be.

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