Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

sanity_check_batch

[Wicked Sanity] Verify up to 50 claims against one shared context in a single call — prefer this over one sanity_check per sentence. data is a list in the same order as claims.

Use when you have a multi-sentence output to verify against one shared context in a single call (up to 50 claims). Not for a single claim (use sanity_check).

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": {
      "claims": "<claims>"
    },
    "name": "sanity_check_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo"grounded" (default; check against context) or "open" (check against live web evidence — consistency with the web, not objective truth).
claimsYes1-50 statements, each up to 5,000 chars.
contextNoSource text the claim(s) must be faithful to. Required for mode "grounded".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real context beyond annotations by disclosing that it "writes state upstream (not read-only)" and requires credentials or a wallet signature. The openWorldHint=true is also indirectly supported by the schema's "open" mode description. Minor deduction because "the credentials or wallet signature noted above where applicable" points to text that does not exist in the description, leaving the exact auth requirement unresolved.

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

Conciseness3/5

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

The opening sentence and the "Use when..." paragraph repeat the same facts (50 claims, one shared context, single call) nearly verbatim. The dangling "noted above" reference also costs space without adding information. The core routing guidance is front-loaded, which saves it from a lower score.

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?

Batch verification semantics and the grounded/open modes are covered, and there is no output schema to relieve. However, with no output schema the description should say what comes back per claim (verdicts, ordering, partial failures), and the dangling auth reference leaves an operational question open.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description introduces "`data` is a list in the same order as `claims`" — there is no `data` parameter in the schema. This actively misleads an agent about what to send. The one genuinely useful hint, batch ordering, is attached to a nonexistent field.

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?

States a specific verb and resource with scope: "Verify up to 50 claims against one shared context in a single call." It also names the sibling it replaces (one sanity_check per sentence), so an agent can distinguish it from sanity_check 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?

Explicit routing in both directions: "Use when you have a multi-sentence output to verify against one shared context" and "Not for a single claim (use sanity_check)." The alternative and the condition that selects it are stated outright.

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