Skip to main content
Glama
Sign In

RubiConnect

by com.rubiconnect.console
OverviewDiscussionsAdmin

get_flow_detail

Retrieves the complete structure of a specific conversation flow by its name or ID, including all nodes, edges, referenced templates, human-readable step summary, and live validation status.

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": {
      "flowIdentifier": "<flowIdentifier>"
    },
    "name": "get_flow_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdNoAgent ID or display name. Defaults to the active agent in context.
flowIdentifierYesName or unique ID of the flow to inspect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the response includes live validation status (useful, non-obvious behavior) and implies a read-only inspection, but never states safety profile, permissions required, or whether validation is computed live on each call.

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 front-loaded sentence with no filler; each listed element (nodes, edges, templates, summary, validation) tells the agent something about the response. Slightly list-heavy but efficient.

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?

No output schema exists, so the description usefully enumerates the returned structure and live validation status. Given the simple two-parameter read operation, only usage routing against siblings is missing.

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 fully documented in the schema. The description only echoes that a name or ID is accepted and omits agentId scoping, adding no meaning beyond structured data; baseline 3 applies.

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 (retrieves) and resource (a single conversation flow) and enumerates the payload: nodes, edges, templates, step summary, validation status. This clearly separates it from list_flows or get_template_detail, though it does not name those siblings explicitly.

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?

Phrasing 'a specific conversation flow by its name or ID' implies inspecting one flow rather than listing many, but there is no explicit when-to-use guidance, no prerequisites, and no named alternative for agents weighing this against list_flows or update_flow.

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

All RubiConnect toolsInspect
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