Skip to main content
Glama

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

artefact_correspondence_criteria

The published criteria for the Artefact Correspondence service (run-artefact-correspondence/v1): the Class A/B claim types and grades, the normalisation rules N1-N6, the NOT-ASSESSABLE list, and the pinned public test corpus identity. Read these before paying - every grade is reproducible from them. - no payment required: call directly without payment (no x402 challenge; this tool is free). HTTP equivalent: GET https://exchangerebel.com/toll/artefact-correspondence/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": "artefact_correspondence_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that no x402 payment challenge is involved, that it is free to call directly, and gives the HTTP equivalent, but it says nothing about response format, read-only semantics, or any other behavioral trait.

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?

Front-loads the resource and its contents, then adds usage and payment notes. Slight redundancy between 'read these before paying' and 'no payment required', and the bullet-style payment note is a bit clunky, but it remains efficient.

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, free criteria-retrieval tool without an output schema, the description is sufficiently complete: it identifies the service, lists the contents, and clarifies the payment behavior. It could be stronger by specifying the response format, but the essential 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?

The tool has zero parameters, so the baseline is 4. The description adds context about what the retrieved criteria cover, though there are no parameters to clarify.

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 resource—the published criteria for the Artefact Correspondence service—and enumerates what it contains (Class A/B claim types, grades, N1-N6 rules, NOT-ASSESSABLE list, corpus identity). It does not explicitly name the sibling check/precheck tools, so differentiation relies on the 'read before paying' hint.

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?

Explicitly says to read these before paying, which implies it should be called before the paid check tool, and it clarifies no payment is required. It does not state when not to use it or name the alternative check tool outright.

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