CNAPS.ai MCP Server

fork_card

Copy a home-page card into the user's workspace as a flow, ready to run. Returns flow_id, the inputs to fill (each with the node_id run_flow keys its inputs by) and the settings the card lets you change. Then upload_file → run_flow(flow_id, inputs) → get_flow(view="status", wait_seconds=20). The flow appears in the user's flow list, so it can also be opened and edited in Studio. Get card_id from search_cards.

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": {
      "card_id": "<card_id>"
    },
    "name": "fork_card"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the card title the new flow is named after, e.g. 'ko' (default en).
`card_id`	Yes	The card id from search_cards (e.g. 'background-remover').

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Well beyond the annotations, it discloses the returned payload (flow_id, inputs keyed by node_id, editable settings) and the persistent side effect that the new flow lands in the user's flow list and is editable in Studio. It also notes the flow is 'ready to run,' telling the agent no extra configuration step is required before run_flow.

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 purpose, then the return shape, then the call chain, then the side effect – a sensible ordering with no filler. The chained-call sentence is dense but each clause carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-trivial mutating tool with no output schema, the description still explains the return values, the required follow-up chain, and the persistence consequence. An agent has everything needed to call it and continue the workflow without guessing.

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 coverage is 100%, so both parameters are already documented, and the description only restates where card_id comes from ('search_cards'), which duplicates the schema text. The lang parameter, which controls the language of the title the flow is named after, is not discussed in the description at all.

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: 'Copy a home-page card into the user's workspace as a flow, ready to run.' The resource noun ('home-page card') implicitly separates it from fork_community_flow and fork_template, but neither sibling is named, so an agent must infer that distinction from the card noun rather than being told explicitly.

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 a clear prerequisite ('Get card_id from search_cards') and an explicit downstream sequence: upload_file → run_flow(flow_id, inputs) → get_flow(view="status", wait_seconds=20). It does not state when a card should be forked instead of a template or community flow, leaving the alternative-path decision to the agent.

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

All CNAPS.ai MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?