Sergio by Serviche

Archive or un-archive a flow

set_flow_archived

Idempotent

Archives a flow as its Archive on the Automations page does (archived true): it leaves the flow pickers and the router but is kept, and runs in progress are unaffected. archived false un-archives it. flow_id comes from read('flows'); archive several by calling once per flow. Pass the same idempotency_key when retrying.

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": {
      "flow_id": "<flow_id>",
      "archived": "<archived>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "set_flow_archived"
  }
}

Input Schema

Name	Required	Description
`flow_id`	Yes
`archived`	Yes
`idempotency_key`	Yes	Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, but the description goes well beyond them by explaining the observable consequences: the flow leaves pickers and the router, is retained, and in-progress runs are unaffected. That reversibility and side-effect profile is exactly the context annotations cannot convey; only the retry/idempotency mechanics are restated rather than added to.

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-loaded with the core action and its effect in the first sentence, then batching and retry guidance, with no filler. The opening sentence is slightly run-on with its parenthetical and subordinate clause, but every sentence carries 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 three-parameter mutation with no output schema, the description covers the effect, reversibility, side effects on running work, batching, ID provenance, and retry semantics. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (only idempotency_key is self-documented), yet the description supplies meaning for the other two: flow_id's provenance via read('flows') and archived's true/false semantics with their concrete effects. The value is meaningful rather than decorative, though it doesn't specify the error behavior of archived=false on an already-active flow.

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?

States a specific verb and resource ('Archives a flow') and immediately disambiguates the boolean's polarity with '(archived true)' followed by 'archived false un-archives it'. It also distinguishes this from deletion ('is kept') and from editing, so an agent can tell it apart from edit_flow or remove_conversation_flow without opening any schema.

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 operating guidance: obtain flow_id from read('flows'), archive multiple flows by calling once per flow, and reuse the same idempotency_key on retries. It never explicitly rules out alternatives (e.g. deletion vs archiving, or the other flow tools), so it stops short of full when/when-not routing.

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

All Sergio by Serviche 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?