Synthex Forge — x402 Paid Agent Services

Extract Invoice Fields

extract_invoice_fields

Read-onlyIdempotent

Utils Invoice Extract. use it rather than extract_invoice_text for invoice fields, not invoice text; an object with 14 fields including amount, currency. $0.1 USDC.

Input Schema

Name	Required	Description	Default
`text`	No	The source text the operation operates on.

Output Schema

Name	Required	Description
`date`	No	The `date` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`amount`	No	The `amount` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`vendor`	No	The `vendor` field of the response.
`utility`	No	The `utility` field of the response.
`currency`	No	The `currency` field of the response.
`invoice_id`	No	The `invoice_id` field of the response.
`line_items`	No	The `line_items` field of the response.
`description`	No	The `description` field of the response.
`raw_preview`	No	The `raw_preview` field of the response.
`utility_result`	No	The `utility_result` field of the response.
`raw_text_preview`	No	The `raw_text_preview` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 31, 2026

addedOutput schema / properties / amount

Added value: +{
+  "description": "The `amount` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / currency

Added value: +{
+  "description": "The `currency` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / date

Added value: +{
+  "description": "The `date` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / description

Added value: +{
+  "description": "The `description` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / invoice_id

Added value: +{
+  "description": "The `invoice_id` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / kind

Added value: +{
+  "description": "The `kind` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / line_items

Added value: +{
+  "description": "The `line_items` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / raw_preview

Added value: +{
+  "description": "The `raw_preview` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / raw_text_preview

Added value: +{
+  "description": "The `raw_text_preview` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / utility

Added value: +{
+  "description": "The `utility` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / utility_result

Added value: +{
+  "description": "The `utility_result` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / vendor

Added value: +{
+  "description": "The `vendor` field of the response.",
+  "type": "object"
+}

addedOutput schema / required
```
Added value: +[
+  "detail"
+]
```

AddedOct 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the description only needs to add context beyond that. It usefully adds the output shape and the cost of $0.1 USDC, which are operationally relevant details not expressed in the annotations.

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 short and mostly front-loaded, with the sibling distinction and cost communicated efficiently. The opening 'Utils Invoice Extract' is slightly clunky, but it does not waste much space.

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?

With an output schema present, the description need not enumerate return fields in detail, and the schema fully documents the single input parameter. The description adds the sibling comparison and cost, covering the main selection and operational concerns for this extraction tool.

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?

There is a single `text` parameter with 100% schema description coverage, so the schema already carries the parameter semantics. The description does not add format guidance or constraints beyond what the schema provides, making the baseline 3 appropriate.

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 identifies the resource as invoice fields and explicitly distinguishes it from extracting invoice text, including a hint about the output shape (14 fields including amount and currency). The opening phrase 'Utils Invoice Extract' is awkward, but the remaining content makes the purpose clear enough to select it over the sibling.

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?

It explicitly says to use this tool rather than `extract_invoice_text` when the goal is invoice fields rather than invoice text. The alternative and selection condition are both stated directly, leaving no ambiguity.

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

All Synthex Forge — x402 Paid Agent Services 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.