Skip to main content
Glama

ComOS Federation

by io.github.ronrey
OverviewDiscussionsAdmin

federation_act

Destructive

Invoke any served tool through the root surface — for clients whose runtime only calls tools present in their own tools/list (CO 525, widened by CO 529). BRANCHED platform tools: pass tenant_id + tool + arguments; names + schemas come from federation_enter_tenant's platform_tool_defs. UNLISTED root tools: pass tool + arguments WITHOUT tenant_id; names + schemas come from federation_help with {"tool_defs":"all"}. Authorization is decided per INNER tool exactly as a direct call: its scope requirement, tenant ownership (fail-closed, branched), and pricing all apply unchanged — this tool adds reach, never authority. Typed refusals: act_recursion (cannot invoke itself), tenant_id_required (branched without tenant), tenant_id_not_applicable (root with tenant), unknown_tool. Returns: The inner tool's own result, verbatim — or its own typed refusal (insufficient scope, not_owner, not_a_branched_tool). Example: call federation_act with arguments {"tenant_id":"","tool":""}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYesThe tool to invoke: a branched platform tool (names/schemas from federation_enter_tenant's platform_tool_defs, e.g. 'booking_status') or an unlisted root tool (names/schemas from federation_help with tool_defs).
argumentsNoThe inner tool's own arguments, exactly as its schema defines them.
tenant_idNoREQUIRED for branched platform tools: the tenant whose composed surface serves the tool (from federation_list_tenants / federation_enter_tenant). OMIT for root tools.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / tenant_id / description
      Previous value: -"The tenant whose composed surface serves the tool (from federation_list_tenants / federation_enter_tenant)."New value: +"REQUIRED for branched platform tools: the tenant whose composed surface serves the tool (from federation_list_tenants / federation_enter_tenant). OMIT for root tools."
    • changedInput schema / properties / tool / description
      Previous value: -"The branched platform tool to invoke (e.g. 'booking_status', 'workflow_run') — names and schemas come from federation_enter_tenant's platform_tool_defs."New value: +"The tool to invoke: a branched platform tool (names/schemas from federation_enter_tenant's platform_tool_defs, e.g. 'booking_status') or an unlisted root tool (names/schemas from federation_help with tool_defs)."
    • changedInput schema / required
      Previous value: -[
-  "tenant_id",
-  "tool"
-]New value: +[
+  "tool"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description goes well beyond: it states authorization is per-inner-tool (scope, fail-closed tenant ownership, pricing apply unchanged), that it adds reach but never authority, and enumerates typed refusals. It also discloses that the inner tool's result is returned verbatim.

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 core purpose, then branches into mode-specific rules, authorization guarantees, and refusals. Dense but every clause carries decision-relevant information; slightly lengthy for a single description but no obvious filler.

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?

Given a mutation tool with no output schema, the description covers invocation modes, parameter routing, authorization semantics, failure modes, and return behavior (inner result verbatim). An agent has everything needed to call it correctly under either client configuration.

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 100%, so baseline is 3. The description adds meaningful usage context beyond the schema: which mode requires tenant_id and which omits it, and how the 'tool' argument's namespace depends on the chosen path (platform_tool_defs vs federation_help with tool_defs), plus the example call.

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 (invoke) and resource (any served tool through the root surface), with a clear audience qualifier (list-gated clients, CO 525/529). Distinguishes the two invocation modes (branched vs unlisted root) and names the sibling tools that provide the names/schemas (federation_enter_tenant, federation_help).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing rules: pass tenant_id + tool + arguments for branched platform tools; omit tenant_id for unlisted root tools. Where to obtain names/schemas is named for each path, and typed refusals (tenant_id_required, tenant_id_not_applicable) encode the when-not conditions.

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

All ComOS Federation 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