Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

agent_compose_pipeline

[$0.25] Run a 2-4 step agent workflow (allowlisted paid routes or preset like safe_swap) in one settled call with synthesized composite_verdict and pipeline_summary.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agent_compose_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget chain ('base' or 'ethereum')base
stepsNoOptional JSON array of 2-4 allowlisted route paths or {route, params} objects
presetNoNamed pipeline preset ('safe_swap' or 'counterparty_audit')safe_swap
fail_fastNoAbort remaining steps on sub-step HTTP >= 400 (default true)
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data
subject_addressNoTarget EVM address (0x...)0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the pricing ($0.25) and that the call is settled, which is real value. It does not explain what 'allowlisted' means, what happens on partial failure beyond the schema's fail_fast note, or what the synthesized verdict looks like, leaving meaningful behavioral gaps.

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?

A single dense sentence with the price and core action front-loaded and no filler. It is packed but not bloated, though the parenthetical adds parsing load compared with a cleaner clause.

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 6-parameter orchestration tool with no output schema, naming the return fields (composite_verdict, pipeline_summary) is helpful, and the description signals the composite/settled nature. It still omits what a degraded or partial-failure result looks like, how steps compose, and any permission requirements, which matters more than usual given the absence of both annotations and an output schema.

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 every parameter is already documented, giving a baseline of 3. The description only echoes terms already in the schema ('allowlisted route paths', 'safe_swap') without adding syntax examples or interaction rules between steps and preset.

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 and resource: 'Run a 2-4 step agent workflow' with the allowable inputs (allowlisted paid routes or a preset like safe_swap) and the produced artifacts (composite_verdict, pipeline_summary). The only gap is that it does not explicitly contrast with single-route or preflight siblings, so differentiation is inferred rather than stated.

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?

Usage is implied by '2-4 step agent workflow ... in one settled call', which signals batching multiple route calls into one paid, settled invocation, and the '$0.25' price hints at a cost tradeoff. However, there is no explicit when-to-use versus running routes individually, no when-not, and no named alternative tool.

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.

Resources