Genexxis paid agent tools (x402)

dealdocs_redflags

Red-flag review of a deal document (term sheet, SAFE, SHA, LOI, SPA/APA, NDA): parties, key terms with clause refs, red flags graded high/medium/low with verbatim quote, market standard and fix, missing protections, questions to ask, from your chosen side. Up to 25 PDF pages / 2.5 MB / 100k characters (larger: /redflags/pro). Long jobs return a free poll URL. Documents are not stored. Price: $0.99 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"
  }
}

Input Schema

Name	Required	Description
`url`	No	https link to the document (PDF, HTML or plain text)
`text`	No	Document text (min 200 characters). Send exactly one of text, url, pdf_base64.
`docType`	No	Optional hint: auto, term_sheet, safe_or_convertible, shareholders_agreement, loi_or_offer, spa_or_apa, nda
`language`	No	Optional output language: auto, en, fr, es, de, it, pt, nl, ar; default auto (language of the document)
`pdf_base64`	No	The PDF file, base64-encoded
`perspective`	No	Optional, red flags only: whose side to review for (neutral, investor, founder, company, buyer, seller, lender, borrower, minority_shareholder, majority_shareholder); default neutral

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.1/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 and does so well: it discloses processing limits (25 PDF pages / 2.5 MB / 100k characters), async behavior ('long jobs return a free poll URL'), a data-retention guarantee ('Documents are not stored'), and payment terms ($0.99 USDC via x402 on Base). It stops short of describing failure/refund behavior or expected latency, which is why it is not a 5.

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?

Dense but front-loaded: purpose first, then output contents, then limits, async behavior, data handling, and pricing. Almost every clause carries operational information; the parenthetical document-type list is long but each item earns its place as a scope signal.

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 six-parameter, no-output-schema tool that costs money per call, the definition covers what is produced, how large an input is allowed, what happens on long jobs, retention, and price. The remaining gap is failure/error handling and the shape of the poll response, which an agent must discover at call time.

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 description coverage is 100%, so every parameter is already documented, and the description mostly restates that surface. It adds modest value by framing 'perspective' as 'from your chosen side' and listing the supported document types, but contributes no format, precedence, or mutual-exclusivity detail beyond the schema.

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 ('Red-flag review of a deal document') and enumerates the covered document types (term sheet, SAFE, SHA, LOI, SPA/APA, NDA). It also names the concrete output artifacts (key terms with clause refs, graded red flags with verbatim quotes, missing protections), which no sibling provides, making it distinguishable from dealdocs_financials at a glance.

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 routes oversized inputs to the alternative ('larger: /redflags/pro') with the exact thresholds that trigger it, and states the perspective selection. It does not distinguish itself from dealdocs_redflags_lite, but the size-based escalation rule is a clear when-to-use boundary.

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?