Skip to main content
Glama

ExchangeRebel — pay-per-call APIs for AI agents (x402 on Solana)

demand_verdict_criteria

The published criteria for the Demand Verdict service (demand-verdict/v1): the rules every paid answer is reproducible from, and the pinned public test corpus identity. - no payment required: call directly without payment (no x402 challenge; this tool is free). HTTP equivalent: GET https://exchangerebel.com/toll/demand-verdict/criteria.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does deliver two genuinely useful behavioral facts: the call is free with no x402 challenge, and the payload is stable/published (pinned corpus identity). It does not say whether the response is JSON or prose, whether it changes across versions, or how a caller should consume the pinned corpus, leaving notable gaps for a zero-annotation tool.

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

Conciseness5/5

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

Two short sentences, front-loaded with the resource identity, followed by the payment status and the HTTP equivalent — the latter being directly actionable for an agent. The only minor redundancy is 'no payment required' restated as 'call directly without payment,' which is small and clarifying.

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, read-only criteria fetch with no output schema, the description covers what it returns, its version, and its cost model, which is what an agent needs to invoke it confidently. It falls short only in not stating the response shape or its relationship to the precheck/verdict siblings.

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?

The tool takes no parameters, so there is no parameter meaning to add and the schema imposes no burden. The description reasonably does not spend words on arguments and instead spends them on what the resource is.

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?

The description names the specific resource — the published criteria for the Demand Verdict service (demand-verdict/v1) — and characterizes its content as the reproducibility rules for paid answers plus the pinned public test corpus identity. That is enough for an agent to know this returns a criteria document rather than running a verdict, though it never explicitly contrasts itself with the sibling tools demand_verdict_precheck and demand_verdict_verdict.

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

Usage Guidelines3/5

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

The only usage guidance is the 'no payment required: call directly without payment (no x402 challenge; this tool is free)' note, which usefully tells the agent it can invoke this without a payment flow. There is no statement of when to fetch criteria versus calling precheck or verdict, and no ordering or prerequisite guidance in the workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources