eds-mcp-server

Overview Schema Source Related Servers Discussions Admin

Compose a flow

compose_flow

Assembles a dependency-resolved flow from component IDs, adding decision registers and regulatory tokens. Builds end-to-end KYC, order, or onboarding surfaces.

Instructions

Assemble a multi-component flow from a list of ids: dependency-resolved order (deps first), per-step decision register, and the union of tokens + regulatory anchors across the flow. For building a KYC / order / onboarding surface end to end.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "compose_flow"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes
`name`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.17.0Jul 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Without annotations, the description carries the full burden. It discloses behavioral traits: dependency order resolution, per-step decision register assembly, and merging of tokens and regulatory anchors. This adds meaningful context beyond a simple 'compose flow' label. However, it does not explicitly state whether the operation is read-only or has side effects.

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?

Two sentences: the first details the core logic, the second provides a use case. The description is efficient and front-loaded with key functionality. It could be slightly more structured (e.g., separate parameter guidance) but is not verbose.

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?

Given no output schema and no annotations, the description adequately conveys what the tool returns (dependency order, decision register, token/anchor union). It is sufficiently complete for a flow composition tool, though parameter 'name' lacks explanation.

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?

The description explains the 'ids' parameter as a 'list of ids' for component assembly. However, it does not address the 'name' parameter, and schema description coverage is 0%. The description adds some meaning beyond the schema but is incomplete for all parameters.

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

Purpose5/5

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

The description clearly states the verb 'assemble' and resource 'multi-component flow'. It specifies key operations: dependency-resolved order, per-step decision register, and union of tokens + regulatory anchors. The use case 'building a KYC / order / onboarding surface end to end' distinguishes it from sibling tools like list_components or get_component.

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 description implies usage for assembling a flow from component IDs, with a concrete use case. However, it does not provide explicit guidance on when to use this tool versus alternatives, nor does it list exclusions or prerequisites. The context is clear but lacks proactive direction.

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