Genexxis paid agent tools (x402)

dealdocs_financials_pro

Financial statements extraction and ratio analysis for long documents (annual reports, audited accounts with notes). Pro tier: up to 100 PDF pages / 5 MB / 400k characters, longer output. Long jobs return a free poll URL. Documents are not stored. Price: $4.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_financials_pro"
  }
}

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/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden and does so well: it discloses document size limits, async polling via a free URL for long jobs, non-storage of documents, and precise pricing/payment mechanics via x402. These are exactly the operational traits an agent needs before calling.

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?

The description is dense and front-loaded: purpose first, then Pro capacity, async behavior, privacy, and price. Every sentence carries useful information with no 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?

It covers capacity, async behavior, privacy, and cost, which is strong for a tool without annotations. Since there is no output schema, some return-shape detail is missing, but the description gives enough for correct invocation.

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 all six parameters are already documented in the input schema. The description does not add parameter-level meaning beyond the schema baseline, so the appropriate score is the baseline 3.

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 states a specific verb and resource: financial statements extraction plus ratio analysis. It scopes this to long documents such as annual reports and audited accounts, and the 'Pro tier' wording implicitly distinguishes it from the smaller sibling, but it does not explicitly name dealdocs_financials as the alternative.

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?

Usage is implied by 'for long documents' and the Pro tier limits, so an agent can infer this is for larger inputs. However, there is no explicit when-to-use guidance versus dealdocs_financials or dealdocs_redflags_pro, and no stated exclusions.

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?