Skip to main content
Glama
FTHTrading

Genesis402

by FTHTrading
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Extract the fields YOU name from any text as JSON. Fields no

genesis402_extract_json

Extract specified fields from any text as JSON, returning null for missing values. Turn emails, invoices, or pages into structured data with pay-per-call pricing.

Instructions

Paid (price from the live 402 quote). Extract the fields YOU name from any text as JSON. Fields not present in the text come back null, never invented. Use to turn emails, invoices or pages into structured data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe source text to read, up to 16,000 characters.
fieldsYesThe fields to extract: an object mapping each field name to a short description, e.g. { "invoice_total": "total amount due in USD", "due_date": "ISO date" }.
payment_signatureNoOptional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.2
    • addedInput schema / properties / fields / description
      Added value: +"The fields to extract: an object mapping each field name to a short description, e.g. { \"invoice_total\": \"total amount due in USD\", \"due_date\": \"ISO date\" }."
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it."
    • addedInput schema / properties / text / description
      Added value: +"The source text to read, up to 16,000 characters."
  2. First observedv0.3.1

TDQS

A4/5.0
Behavior4/5

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

The description adds meaningful behavioral context: it is paid and tied to the live 402 quote, and it never invents missing field values ('Fields not present in the text come back null'). This goes beyond what the annotations alone convey, even though the full payment flow is left to the schema.

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 compact and front-loaded with the most critical decision-relevant fact ('Paid'). Each subsequent sentence earns its place: extraction behavior, null/invention guarantee, and recommended use case. There is no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, the description could say more about the exact return shape beyond 'as JSON' and null behavior. It also leaves the quote/signature workflow mostly implicit, but the input schema does document `payment_signature` clearly, so the gap is moderate rather than severe.

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 goes further by explaining what happens to requested fields that are absent from the text—they come back null and are never fabricated—which directly clarifies the semantics of the `fields` parameter.

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 clearly states the verb ('Extract'), the resource ('the fields YOU name'), the input source ('any text'), and the output format ('as JSON'). It also gives concrete use cases ('emails, invoices or pages'), though it does not explicitly distinguish itself from sibling tools like genesis402_web_extract.

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?

'Use to turn emails, invoices or pages into structured data' provides clear context for when to apply this tool. It does not name alternatives or give exclusion criteria, so it stops short of fully explicit routing guidance.

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

Deploy Server

Other Tools