Agent402.Tools: pay-per-call web tools

Decide: execute a plan

decide.execute

Paid ($0.001/call): Run a decision's plan (decisionId from POST /api/decide), or a free plan sketch (steps), through Agent402: first-party steps run directly, third-party steps are bought from the seller and resold to you at Agent402's price (paid with a wallet on Base; prepaid credits and cards do not pay this route).

Input Schema

Name	Required	Description
`steps`	No	Instead of decisionId: the tool slugs of a free plan sketch (from /api/find or /api/route), 2 to 5, in order. Pass params for step 1; a later step takes its one required input from the step before.
`params`	No	Per-step params overriding the plan's exampleParams, keyed by step number
`replan`	No	With decisionId: plan the saved task again on current prices and reliability, then run the new plan. Adds the plan price for that decision's depth to the quote; the answer's replanned field lists what changed. Default false.
`decisionId`	No	From POST /api/decide (or pass steps instead)
`creditToken`	No	executionCredit.token from that decision (optional)
`maxBudgetUsd`	No	Spend ceiling for the run (default: the plan's estimate via Agent402)

Output Schema

Name	Required	Description	Default
`runId`	No
`steps`	No
`status`	No
`paidUsd`	No
`spentUsd`	No
`budgetUsd`	No
`decisionId`	No
`routingFeePct`	No
`leftoverCredit`	No
`creditAppliedUsd`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / replan

Added value: +{
+  "description": "With decisionId: plan the saved task again on current prices and reliability, then run the new plan. Adds the plan price for that decision's depth to the quote; the answer's replanned field lists what changed. Default false.",
+  "type": "boolean"
+}

Changed3 schema fields changedOct 9, 2026

changedInput schema / properties / decisionId / description

Previous value: -"From POST /api/decide"New value: +"From POST /api/decide (or pass steps instead)"

addedInput schema / properties / steps

Added value: +{
+  "description": "Instead of decisionId: the tool slugs of a free plan sketch (from /api/find or /api/route), 2 to 5, in order. Pass params for step 1; a later step takes its one required input from the step before.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "decisionId"
-]New value: +[]

AddedSep 30, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes far beyond the annotations: discloses the $0.001/call price, the resale economics of third-party steps, that payment must come from a Base wallet and cannot use prepaid credits or cards, and that replan adds a plan price. None of this is in the annotations, and nothing contradicts them (readOnly=false, openWorld=true, non-idempotent all fit an execution tool).

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?

Front-loads the paid price and the verb, and the single long sentence carries no filler. It is dense and heavily nested with parentheticals, which slightly hinders scanning, but every clause adds operational information.

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 a rich schema, an output schema, and annotations already covering safety, the description still supplies the payment mechanics and route selection an agent needs. It omits failure and retry semantics for a non-idempotent, money-spending run, which is the main remaining gap.

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 schema already documents all six parameters including steps, params, replan, decisionId, creditToken, and maxBudgetUsd. The description adds only the '2 to 5' step-count hint and no format or semantics beyond what the schema provides, making the baseline 3 the right call.

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?

States a specific verb (run/execute) and resource (a decision's plan or a free plan sketch) and explains the two input paths, so an agent can distinguish it from decide.plan, which only plans. It never names the sibling tool decide.plan directly, citing 'POST /api/decide' instead, which is a small differentiation gap.

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 concrete guidance on which input path to use ('decisionId from POST /api/decide, or a free plan sketch (steps)') and where the steps come from (/api/find or /api/route). It does not state when to avoid this tool or when replan=true is preferable beyond a one-line default, so it falls short of full when/when-not coverage.

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

All Agent402.Tools: pay-per-call web tools tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.