Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

protocol_health_refresh_all

Force an immediate live re-score of every tracked protocol instead of waiting for the scheduled refresh. Use this when you need all protocol health scores updated now, not a single protocol.

Instructions

[Protocol Health Oracle] Force an immediate live re-score of all tracked protocols.

Use when you need every tracked protocol re-scored right now instead of waiting for the schedule. Not for a single protocol (read it with protocol_health_score).

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior4/5

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

The description adds useful context beyond annotations by stating that it writes state upstream and may require credentials or a wallet signature. The auth note is somewhat vague with 'where applicable,' but the write behavior and non-read-only nature are clearly disclosed and consistent with annotations.

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?

The description is front-loaded and efficient: purpose first, then when-to-use, then the single-protocol exclusion, then behavior. The phrase 'noted above where applicable' is slightly vague but does not bloat the 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 zero-parameter action tool, the description covers purpose, usage, scope, and write behavior. Since there is no output schema, it could say more about what the refresh returns, but the essential invocation context is present.

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?

There are no parameters to explain, so the baseline is 4. The description correctly presents this as a zero-input bulk action.

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?

The description uses a specific verb and resource: force an immediate live re-score of all tracked protocols. It also explicitly distinguishes this bulk refresh from the single-protocol sibling, protocol_health_score.

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?

It states exactly when to use it: when every tracked protocol must be re-scored now rather than waiting for the schedule. It also names the alternative for a single protocol, protocol_health_score.

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

Deploy Server

Other Tools