Create a multi-step transaction chain. Chains allow sequential service invocations with output piping. Phase 3 — not yet implemented.
| Name | Required | Description | Default |
|---|---|---|---|
| steps | Yes | JSON array of chain steps (service_id + input mappings) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses a critical behavioral trait by noting 'Phase 3 — not yet implemented,' warning agents that calling it may fail. However, it does not mention side effects, permissions, or return behavior, leaving significant behavioral aspects undisclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, with only two short sentences plus a caveat. It is front-loaded with the verb and purpose, and every sentence adds value: purpose, mechanism, and implementation status. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with one parameter and no output schema, the description provides the essential purpose and a key caveat about implementation status. However, it omits expected return values, error behavior, and any prerequisites or limitations beyond 'not yet implemented,' leaving the agent somewhat in the dark about what will happen if invoked.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the only parameter 'steps' with a full description ('JSON array of chain steps (service_id + input mappings)'), achieving 100% schema description coverage. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states with a specific verb ('Create') and resource ('multi-step transaction chain'), and explains that chains allow sequential service invocations with output piping, which distinguishes it from sibling tools like ae_create_transaction. However, it doesn't explicitly contrast with alternatives, so a high but not perfect score is given.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for sequential service invocations and output piping, but provides no explicit guidance on when to use this versus ae_create_transaction or other alternatives. It lacks exclusions or when-not-to-use conditions, making the usage guidance merely implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action, from service discovery and registration to transaction negotiation and output verification. The only overlapping pair, ae_discover_services and ae_list_services, is explicitly differentiated by semantic search vs. categorical browsing.
All tools follow the consistent ae_verb_noun pattern in snake_case, with verbs like create, get, list, deliver, and verify. The uniform prefix and naming convention make the API predictable and easy to navigate.
With 13 tools, the server is well-scoped for a marketplace platform, covering service lifecycle, transaction workflow, wallet, trust, and agent management. Each tool serves a distinct purpose and none feel redundant, keeping the surface area manageable.
The tool set covers the full service and transaction lifecycle: register/list/discover/get services, create/negotiate/deliver/verify transactions, plus wallet and trust queries. Minor gaps exist such as no service update/delete or transaction listing, but core workflows are fully supported.