Genexxis paid agent tools (x402)

dealdocs_redflags_lite

Quick red-flag scan of a term sheet, SAFE, SHA, LOI, SPA or NDA (English or French text/HTML URL, or text up to 6000 chars): document type, heuristic risk, top 3 risky clauses quoted (participating or >1x preference, full ratchet, personal guarantee, redemption, drag-along, vetoes...) and why they matter. Keyword scan, no AI. Full AI review: POST /redflags. Price: $0.005 USDC per call, paid with x402 on Base.

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

Input Schema

Name	Required	Description	Default
`url`	No	https link to an HTML or plain-text deal document (PDF: use POST /redflags)
`text`	No	or the document text, 200-6000 characters

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4/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 load and does so well: it discloses the keyword-scan/heuristic method ("no AI"), the character limit, the unsupported input (PDF), the return shape (type, risk level, top-3 quoted clauses), and the x402 payment cost on Base. Cost and payment mechanism are exactly the kind of context annotations would otherwise supply; only rate/error behavior is unspecified.

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?

One dense sentence covering input types, outputs, and caveats, followed by two short sentences for the method, the alternative, and the price. Front-loaded with the action; nothing is filler.

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?

Covers inputs, limits, output contents, method, cost, and the escalation path, with no output schema to defer to on return values. The only missing piece is guidance on choosing between this and the pro/AI variants beyond the single POST /redflags pointer.

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

Parameters3/5

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

Schema coverage is 100%, so both params are already documented. The description restates the 6000-char cap and the PDF exclusion that the schema itself states; no additional format or precedence rules (e.g., whether url or text wins if both are supplied) are added, so baseline 3 applies.

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 verb and resource ("Quick red-flag scan") and enumerates the document types covered (term sheet, SAFE, SHA, LOI, SPA, NDA) plus the deliverable (doc type, heuristic risk, top 3 risky clauses). Differentiation from the AI siblings is only implicit via "lite"/"no AI" and the pointer to POST /redflags, not an explicit sibling comparison.

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?

Gives usable preconditions: English or French, HTML/plain-text URL or text up to 6000 chars, and routes PDFs and deeper analysis to POST /redflags. It never says when to pick this over dealdocs_redflags_pro, which is the main remaining gap.

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

All Genexxis paid agent tools (x402) tools Inspect

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

Need Help?