Synthex Forge — x402 Paid Agent Services

Assess Tender Eligibility

assess_tender_eligibility

Read-onlyIdempotent

Evaluate a company against supplied tender criteria. use it rather than assess_grant_eligibility for tender eligibility, not grant eligibility; an object with 38 fields including applicant_id, comparator. $0.25 USDC.

Input Schema

Name	Required	Description
`criteria`	No	The criteria the eligibility decision is measured against.
`evidence`	No	The evidence supporting the claim, as a list of named documents or URLs.
`applicant_id`	No	The applicant's identifier.
`jurisdiction`	No	The jurisdiction the answer applies to. Accepts an ISO-3166 alpha-2 code or a country name.
`applicant_documents`	No	The applicant's supporting documents.

Output Schema

Name	Required	Description
`gap`	No	The `gap` field of the response.
`met`	No	The `met` field of the response.
`kind`	No	The `kind` field of the response.
`type`	No	The `type` field of the response.
`quote`	No	The `quote` field of the response.
`value`	No	The `value` field of the response.
`counts`	No	The `counts` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`reason`	No	Why the verdict was reached.
`not_met`	No	The `not_met` field of the response.
`unclear`	No	The `unclear` field of the response.
`verdict`	Yes	The decision this tool returned.
`criteria`	No	The `criteria` field of the response.
`document`	No	The `document` field of the response.
`expected`	No	The `expected` field of the response.
`exception`	No	The `exception` field of the response.
`mandatory`	No	The `mandatory` field of the response.
`threshold`	No	The `threshold` field of the response.
`comparator`	No	The `comparator` field of the response.
`comparison`	No	The `comparison` field of the response.
`description`	No	The `description` field of the response.
`applicant_id`	No	The `applicant_id` field of the response.
`criterion_id`	No	The `criterion_id` field of the response.
`jurisdiction`	No	The `jurisdiction` field of the response.
`unverifiable`	No	The `unverifiable` field of the response.
`disqualifying`	No	The `disqualifying` field of the response.
`criteria_total`	No	The `criteria_total` field of the response.
`evidence_quote`	No	The `evidence_quote` field of the response.
`evidence_value`	No	The `evidence_value` field of the response.
`criteria_judged`	No	The `criteria_judged` field of the response.
`optional_failed`	No	The `optional_failed` field of the response.
`mandatory_failed`	No	The `mandatory_failed` field of the response.
`evidence_document`	No	The `evidence_document` field of the response.
`evidence_supplied`	No	The `evidence_supplied` field of the response.
`missing_documents`	No	The `missing_documents` field of the response.
`criteria_unverifiable`	No	The `criteria_unverifiable` field of the response.
`mandatory_unverifiable`	No	The `mandatory_unverifiable` field of the response.
`missing_document_count`	No	The `missing_document_count` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed40 schema fields changedOct 31, 2026

addedOutput schema / properties / applicant_id

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

addedOutput schema / properties / comparator

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

addedOutput schema / properties / comparison

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

addedOutput schema / properties / counts

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

addedOutput schema / properties / criteria

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

addedOutput schema / properties / criteria_judged

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

addedOutput schema / properties / criteria_total

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

addedOutput schema / properties / criteria_unverifiable

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

addedOutput schema / properties / criterion_id

Added value: +{
+  "description": "The `criterion_id` 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 / disqualifying

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

addedOutput schema / properties / document

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

addedOutput schema / properties / evidence_document

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

addedOutput schema / properties / evidence_quote

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

addedOutput schema / properties / evidence_supplied

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

addedOutput schema / properties / evidence_value

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

addedOutput schema / properties / exception

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

addedOutput schema / properties / expected

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

addedOutput schema / properties / gap

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

addedOutput schema / properties / jurisdiction

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / mandatory

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

addedOutput schema / properties / mandatory_failed

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

addedOutput schema / properties / mandatory_unverifiable

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

addedOutput schema / properties / met

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

addedOutput schema / properties / missing_document_count

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

addedOutput schema / properties / missing_documents

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

addedOutput schema / properties / not_met

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

addedOutput schema / properties / optional_failed

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

addedOutput schema / properties / quote

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

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

removedOutput schema / properties / status

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

addedOutput schema / properties / threshold

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

addedOutput schema / properties / type

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

addedOutput schema / properties / unclear

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

addedOutput schema / properties / unverifiable

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

addedOutput schema / properties / value

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

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the description only needs to add context. It contributes two genuinely useful facts not in the annotations: a fixed price of $0.25 USDC and the shape of the return payload (an object with 38 fields). It says nothing about what happens on missing or conflicting evidence, but for a read-only assessment call that is a modest gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short in word count, but the middle clause is a run-on fragment ('...tender eligibility, not grant eligibility; an object with 38 fields...') that repeats the eligibility distinction and blurs the boundary between input and output. The purpose is front-loaded, yet roughly a third of the text is redundant restatement.

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 needn't explain return values, though its mention of the 38-field payload is a harmless hint. For a zero-required-parameter, fully schema-documented, read-only assessment tool, the only meaningful omission is guidance on what to do when criteria or evidence are absent.

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 every parameter is already documented in the schema; a 3 baseline applies. The description names `applicant_id` but pairs it with 'comparator', which is not a parameter at all, making the sentence more likely to describe the response than the inputs. It adds no syntax or format guidance for criteria, evidence or jurisdiction.

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: 'Evaluate a company against supplied tender criteria.' It then explicitly disambiguates from the nearest sibling, `assess_grant_eligibility`, so an agent can route between the two without opening either schema.

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 an explicit when-to-use condition ('for tender eligibility, not grant eligibility') and names the alternative it replaces. It does not address the other plausible siblings such as `assess_business_eligibility`, and the clause is phrased redundantly, but the routing signal is clear.

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.