Skip to main content
Glama

Agent Decision Packet Rail

wever_agent-decision-packet-rail
Destructive

Paid URL: 0.10 USDC per call on Base; 10 signed-wallet free calls shared over rolling 30 days. Read the backend 402 body for x402 terms. Evaluate supplied alternatives against explicit weighted numeric criteria and constraints, with transparent scores, evidence gaps and ties. Operating boundary: Scores use supplied evidence and measurements only. Missing evidence, failed constraints and ties are disclosed. No independent truth or optimality claim. POST /api/agent-decision-packet-rail. Existing product credentials, signed mandates, and single-use action grants remain required where applicable. This adapter grants no authority and never supplies server credentials. Wallet-authenticated bounded operations service with durable records. See /api/operations-contract for exact schemas, verified scope and unavailable capabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
usageYes
optionsYes
criteriaYes
objectiveYes
constraintsYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • removedInput schema / description
      Removed value: -"The existing product POST body. Supply its documented mode, arguments, and required signed authority or grant. The product validates its full contract."
    • removedInput schema / maxProperties
      Removed value: -64
    • removedInput schema / minProperties
      Removed value: -1
    • addedInput schema / properties / constraints
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "criterion_id": {
      +        "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +        "type": "string"
      +      },
      +      "operator": {
      +        "enum": [
      +          "gte",
      +          "lte"
      +        ]
      +      },
      +      "value": {
      +        "maximum": 1000000000,
      +        "minimum": -1000000000,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "criterion_id",
      +      "operator",
      +      "value"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 32,
      +  "minItems": 0,
      +  "type": "array"
      +}
    • addedInput schema / properties / criteria
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "criterion_id": {
      +        "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +        "type": "string"
      +      },
      +      "direction": {
      +        "enum": [
      +          "maximize",
      +          "minimize"
      +        ]
      +      },
      +      "label": {
      +        "maxLength": 160,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "max_value": {
      +        "maximum": 1000000000,
      +        "minimum": -1000000000,
      +        "type": "integer"
      +      },
      +      "min_value": {
      +        "maximum": 1000000000,
      +        "minimum": -1000000000,
      +        "type": "integer"
      +      },
      +      "weight": {
      +        "maximum": 1000,
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "criterion_id",
      +      "label",
      +      "direction",
      +      "weight",
      +      "min_value",
      +      "max_value"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 16,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +  "type": "string"
      +}
    • addedInput schema / properties / mode / const
      Added value: +"evaluate"
    • removedInput schema / properties / mode / maxLength
      Removed value: -128
    • removedInput schema / properties / mode / minLength
      Removed value: -1
    • removedInput schema / properties / mode / type
      Removed value: -"string"
    • addedInput schema / properties / objective
      Added value: +{
      +  "maxLength": 2000,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / options
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "assessments": {
      +        "items": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "criterion_id": {
      +              "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +              "type": "string"
      +            },
      +            "evidence": {
      +              "items": {
      +                "additionalProperties": false,
      +                "properties": {
      +                  "reference": {
      +                    "maxLength": 256,
      +                    "minLength": 1,
      +                    "type": "string"
      +                  },
      +                  "summary": {
      +                    "maxLength": 512,
      +                    "minLength": 1,
      +                    "type": "string"
      +                  }
      +                },
      +                "required": [
      +                  "reference",
      +                  "summary"
      +                ],
      +                "type": "object"
      +              },
      +              "maxItems": 2,
      +              "minItems": 0,
      +              "type": "array"
      +            },
      +            "value": {
      +              "anyOf": [
      +                {
      +                  "maximum": 1000000000,
      +                  "minimum": -1000000000,
      +                  "type": "integer"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            }
      +          },
      +          "required": [
      +            "criterion_id",
      +            "value",
      +            "evidence"
      +          ],
      +          "type": "object"
      +        },
      +        "maxItems": 16,
      +        "minItems": 1,
      +        "type": "array"
      +      },
      +      "label": {
      +        "maxLength": 160,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "option_id": {
      +        "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "option_id",
      +      "label",
      +      "assessments"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 16,
      +  "minItems": 2,
      +  "type": "array"
      +}
    • addedInput schema / properties / usage
      Added value: +{
      +  "enum": [
      +    "synthetic",
      +    "operational"
      +  ]
      +}
    • addedInput schema / required
      Added value: +[
      +  "idempotency_key",
      +  "usage",
      +  "mode",
      +  "objective",
      +  "criteria",
      +  "constraints",
      +  "options"
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only carry the safety flags (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true). The description adds meaningful context beyond them: 0.10 USDC per call on Base with 10 free signed-wallet calls per rolling 30 days, a 402 x402 billing flow, required credentials/mandates/action grants, 'this adapter grants no authority and never supplies server credentials', and durable records. That is substantial behavioral disclosure beyond the structured fields.

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 core purpose and operating boundary are stated in tight sentences, but the definition leads with billing/402 detail ahead of what the tool actually does, and the closing credential/adapter boilerplate and '/api/operations-contract' pointer dilute the payload.

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?

With 7 required params, a nested-ish schema, 0% schema description coverage and no output schema, the description does well on the output side (discloses scores, evidence gaps, ties, no optimality claim) but leaves the input contract largely unexplained. Adequate for a complex tool, but missing parameter-level completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all 7 required parameters, so the description carries the full burden. It loosely gestures at criteria/constraints/options, but never explains 'mode' (const 'evaluate'), the 'usage' enum (synthetic vs operational), or 'idempotency_key' semantics, so an agent cannot confirm parameter meaning from the prose.

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 second sentence gives a specific verb+resource: 'Evaluate supplied alternatives against explicit weighted numeric criteria and constraints, with transparent scores, evidence gaps and ties.' That tells an agent exactly what the tool computes. It does not explicitly name the sibling it differs from, though the compute-an-evaluation role is distinct from the payment/ledger siblings.

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?

The 'Operating boundary' sets a real constraint on use ('Scores use supplied evidence and measurements only') and the pricing line establishes the pay-per-call model. However, there is no explicit statement of when to choose this over a sibling or when not to invoke it; usage is implied rather than stated.

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.