Skip to main content
Glama

crosscheck

by com.crosscheckapi
OverviewDiscussionsAdmin

Review a draft

check

Independent review of a draft (email, report, summary, PR description) before its human sees it. Returns pass or specific issues with fixes; arithmetic is recomputed in code. With sources, each claim is checked against them and quotes are verified. $0.02. Paid per call in USDC over x402 (Base, or free test USDC on Base Sepolia). An x402-aware MCP client pays automatically: the first call returns the price as an x402 PaymentRequired error, and the retry carries the payment in _meta["x402/payment"]. Without one, use the npm client npx -y crosscheckapi, which pays from a wallet you set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoOptional: the hash of a crosscheck receipt that brought you here. Its wallet earns check credits from your first 90 days of spend.
draftYesThe draft text to review
sourcesNoOptional texts the draft relies on; turns on grounding
open_reviewNoOptional: let a qualified outside reviewer take the job (not routed yet; crosscheck's reviewer does it and the receipt says so)
moltbook_identityNoOptional: a Moltbook identity token for the free tier, when it is on (a verified Moltbook agent gets free checks with no payment). Not stored. Without a free check left, the price comes back as usual

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / moltbook_identity
      Added value: +{
+  "description": "Optional: a Moltbook identity token for the free tier, when it is on (a verified Moltbook agent gets free checks with no payment). Not stored. Without a free check left, the price comes back as usual",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / open_review
      Added value: +{
+  "description": "Optional: let a qualified outside reviewer take the job (not routed yet; crosscheck's reviewer does it and the receipt says so)",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / ref
      Added value: +{
+  "description": "Optional: the hash of a crosscheck receipt that brought you here. Its wallet earns check credits from your first 90 days of spend.",
+  "pattern": "^[0-9a-f]{64}$",
+  "type": "string"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the paid-per-call model, the x402 PaymentRequired error flow, the retry with _meta['x402/payment'], the free tier via moltbook_identity, and the fact that arithmetic is recomputed in code. It does not state whether the operation mutates anything, but the tool is a review/check operation and the description's payment and retry behavior is substantial transparency. A small gap: no explicit statement that it is read-only or that it does not store drafts, though 'Not stored' is mentioned for moltbook_identity.

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 dense but well-structured: it front-loads the core purpose, then covers return behavior, sources, and payment. Every sentence adds information, and the payment explanation is compact despite being complex. It is slightly long, but the complexity of the x402 flow justifies the length. No filler or repetition.

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 tool with no output schema and no annotations, the description covers the main behavioral context: what it returns (pass or issues with fixes), how sources affect it, and how payment works. It does not describe the exact output format or error cases beyond the PaymentRequired error, but the description is strong for a paid review tool. The sibling tools (accept, result, skillcheck, etc.) suggest a workflow, but the description does not need to explain them for this tool to be invoked correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the payment flow tied to the first call, the free tier tied to moltbook_identity, and the grounding behavior tied to sources. It does not add detail for ref or open_review beyond the schema, but the schema already describes those well. The description's added context for sources and payment parameters justifies a 4.

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 opens with a specific verb and resource: 'Independent review of a draft (email, report, summary, PR description) before its human sees it.' It names concrete artifact types and the review's purpose, and it distinguishes the tool from siblings by describing a paid, source-checking review service rather than a generic check. The title 'Review a draft' is expanded into a clear, actionable statement.

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?

The description explicitly explains when to use the tool: before a human sees a draft, and with sources to verify claims and quotes. It also gives payment/usage context: x402-aware clients pay automatically, and the npm client is named as an alternative invocation path. It does not explicitly name sibling tools as alternatives, but it clearly states the conditions for using this tool and how to invoke it.

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

All crosscheck 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