Skip to main content
Glama

Synthex Forge — x402 Paid Agent Services

Execute Route

execute_route
Read-onlyIdempotent

Plan the route. use it rather than assess_operation_behaviour_drift for route, not operation behaviour drift; an object with 56 fields including action, blockers. $0.05 USDC.

Input Schema

NameRequiredDescriptionDefault
intentNoThe commercial intent the operation evaluates.
rail_tableNoThe rail table this operation operates on. See the schema for its type and whether it is required.
constraintsNoHard constraints the result must respect.

Output Schema

NameRequiredDescriptionDefault
feeNoThe `fee` field of the response.
llmNoThe `llm` field of the response.
kindNoThe `kind` field of the response.
planNoThe `plan` field of the response.
railNoThe `rail` field of the response.
stepNoThe `step` field of the response.
clockNoThe `clock` field of the response.
actionNoThe `action` field of the response.
key_idNoThe `key_id` field of the response.
reasonNoWhy the verdict was reached.
sourceNoThe `source` field of the response.
networkNoThe `network` field of the response.
profileNoThe `profile` field of the response.
secondsNoThe `seconds` field of the response.
verdictYesThe decision this tool returned.
blockersNoThe `blockers` field of the response.
verdictsNoThe `verdicts` field of the response.
signatureYesThe Ed25519 signature over the evidence core, base64-encoded.
signed_byNoThe key id that signed the answer.
broadcastsNoThe `broadcasts` field of the response.
constraintNoThe `constraint` field of the response.
executableNoThe `executable` field of the response.
fee_sourceNoThe `fee_source` field of the response.
holds_keysNoThe `holds_keys` field of the response.
public_keyNoThe `public_key` field of the response.
est_fee_usdNoThe `est_fee_usd` field of the response.
est_secondsNoThe `est_seconds` field of the response.
max_fee_usdNoThe `max_fee_usd` field of the response.
max_secondsNoThe `max_seconds` field of the response.
methodologyNoThe `methodology` field of the response.
confirmationsNoThe `confirmations` field of the response.
coverage_gapsNoThe `coverage_gaps` field of the response.
evidence_coreYesThe canonical, signed core of the answer — the payload the signature covers.
output_sha256YesSHA-256 hex digest of the canonical evidence core.
calls_a_walletNoThe `calls_a_wallet` field of the response.
missing_fieldsNoThe `missing_fields` field of the response.
profileVersionNoVersion of the answer profile.
totalEstFeeUsdNoThe `totalEstFeeUsd` field of the response.
profile_versionNoVersion of the answer profile.
railTableSourceNoThe `railTableSource` field of the response.
totalEstSecondsNoThe `totalEstSeconds` field of the response.
canonicalizationNoThe canonicalisation rule the digest was computed under.
default_selectionNoThe `default_selection` field of the response.
executionBoundaryNoThe `executionBoundary` field of the response.
rail_table_sourceNoThe `rail_table_source` field of the response.
total_est_fee_usdNoThe `total_est_fee_usd` field of the response.
total_est_secondsNoThe `total_est_seconds` field of the response.
constraintsAppliedNoThe `constraintsApplied` field of the response.
execution_boundaryNoThe `execution_boundary` field of the response.
methodologyVersionNoThe `methodologyVersion` field of the response.
reads_a_credentialNoThe `reads_a_credential` field of the response.
signs_transactionsNoThe `signs_transactions` field of the response.
touches_the_ledgerNoThe `touches_the_ledger` field of the response.
constraints_appliedNoThe `constraints_applied` field of the response.
methodology_versionNoVersion of the method that produced the answer.
signature_algorithmNoThe `signature_algorithm` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed58 schema fields changed
    • addedOutput schema / properties / action
      Added value: +{
      +  "description": "The `action` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / blockers
      Added value: +{
      +  "description": "The `blockers` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / broadcasts
      Added value: +{
      +  "description": "The `broadcasts` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / calls_a_wallet
      Added value: +{
      +  "description": "The `calls_a_wallet` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / canonicalization
      Added value: +{
      +  "description": "The canonicalisation rule the digest was computed under.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / clock
      Added value: +{
      +  "description": "The `clock` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / confirmations
      Added value: +{
      +  "description": "The `confirmations` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / constraint
      Added value: +{
      +  "description": "The `constraint` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / constraintsApplied
      Added value: +{
      +  "description": "The `constraintsApplied` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / constraints_applied
      Added value: +{
      +  "description": "The `constraints_applied` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverage_gaps
      Added value: +{
      +  "description": "The `coverage_gaps` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / default_selection
      Added value: +{
      +  "description": "The `default_selection` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / est_fee_usd
      Added value: +{
      +  "description": "The `est_fee_usd` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / est_seconds
      Added value: +{
      +  "description": "The `est_seconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / evidence_core
      Added value: +{
      +  "description": "The canonical, signed core of the answer — the payload the signature covers.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / executable
      Added value: +{
      +  "description": "The `executable` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / executionBoundary
      Added value: +{
      +  "description": "The `executionBoundary` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / execution_boundary
      Added value: +{
      +  "description": "The `execution_boundary` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / fee
      Added value: +{
      +  "description": "The `fee` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / fee_source
      Added value: +{
      +  "description": "The `fee_source` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / holds_keys
      Added value: +{
      +  "description": "The `holds_keys` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / key_id
      Added value: +{
      +  "description": "The `key_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 / llm
      Added value: +{
      +  "description": "The `llm` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / max_fee_usd
      Added value: +{
      +  "description": "The `max_fee_usd` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / max_seconds
      Added value: +{
      +  "description": "The `max_seconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / methodology
      Added value: +{
      +  "description": "The `methodology` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / methodologyVersion
      Added value: +{
      +  "description": "The `methodologyVersion` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / methodology_version
      Added value: +{
      +  "description": "Version of the method that produced the answer.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / missing_fields
      Added value: +{
      +  "description": "The `missing_fields` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / network
      Added value: +{
      +  "description": "The `network` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / output_sha256
      Added value: +{
      +  "description": "SHA-256 hex digest of the canonical evidence core.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / plan
      Added value: +{
      +  "description": "The `plan` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / profile
      Added value: +{
      +  "description": "The `profile` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / profileVersion
      Added value: +{
      +  "description": "Version of the answer profile.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / profile_version
      Added value: +{
      +  "description": "Version of the answer profile.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / public_key
      Added value: +{
      +  "description": "The `public_key` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / rail
      Added value: +{
      +  "description": "The `rail` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / railTableSource
      Added value: +{
      +  "description": "The `railTableSource` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / rail_table_source
      Added value: +{
      +  "description": "The `rail_table_source` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reads_a_credential
      Added value: +{
      +  "description": "The `reads_a_credential` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reason
      Added value: +{
      +  "description": "Why the verdict was reached.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / seconds
      Added value: +{
      +  "description": "The `seconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / signature
      Added value: +{
      +  "description": "The Ed25519 signature over the evidence core, base64-encoded.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / signature_algorithm
      Added value: +{
      +  "description": "The `signature_algorithm` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / signed_by
      Added value: +{
      +  "description": "The key id that signed the answer.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / signs_transactions
      Added value: +{
      +  "description": "The `signs_transactions` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / source
      Added value: +{
      +  "description": "The `source` field of the response.",
      +  "type": "object"
      +}
    • removedOutput schema / properties / status
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / step
      Added value: +{
      +  "description": "The `step` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / totalEstFeeUsd
      Added value: +{
      +  "description": "The `totalEstFeeUsd` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / totalEstSeconds
      Added value: +{
      +  "description": "The `totalEstSeconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / total_est_fee_usd
      Added value: +{
      +  "description": "The `total_est_fee_usd` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / total_est_seconds
      Added value: +{
      +  "description": "The `total_est_seconds` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / touches_the_ledger
      Added value: +{
      +  "description": "The `touches_the_ledger` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / verdict
      Added value: +{
      +  "description": "The decision this tool returned.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / verdicts
      Added value: +{
      +  "description": "The `verdicts` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "evidence_core",
      +  "output_sha256",
      +  "signature",
      +  "verdict"
      +]
  2. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false. The description adds the cost ('$0.05 USDC') and mentions an output object with 56 fields, but does not discuss permissions, side effects, or rate limits; with annotations covering safety, this is a modest but useful addition.

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?

The description is short and front-loads the sibling routing, but the sentence structure is fragmented and the clause 'an object with 56 fields including action, blockers' is unclear and arguably redundant because an output schema exists.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with nested objects and three optional parameters, the description does not explain what 'route' means, what the operation actually plans or executes, or how the inputs shape the result. Cost and sibling guidance help, but the core behavioral context is missing.

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 the three parameters are already documented in the schema. The description does not mention `intent`, `rail_table`, or `constraints` and adds no meaning beyond the schema, which is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Plan the route,' which gives a verb and resource but does not explain what a route is, what planning entails, or how this differs from execution implied by the tool name. It does distinguish itself from `assess_operation_behaviour_drift`, but the core purpose remains vague.

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?

It explicitly names an alternative tool and states the condition for choosing this one: use it rather than `assess_operation_behaviour_drift` for route, not operation behaviour drift. That is clear routing guidance, though the phrasing is awkward and no other exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.