Skip to main content
Glama

ComOS Federation Gateway

by com.comos-federation
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"} (the prompt family beyond the listed library read and run — federation_prompt_review, _reviews, _submit — lives here). 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":"<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?

Goes well beyond the annotations: it discloses that authorization is evaluated per inner tool (scope, tenant ownership fail-closed, pricing), that it 'adds reach, never authority', enumerates typed refusals (act_recursion, tenant_id_required, tenant_id_not_applicable, unknown_tool), and states the return is the inner tool's result verbatim or its own refusal.

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?

Purpose and the routing rule are front-loaded, and the density is justified by the branching logic and refusal taxonomy. It loses a point for packed parenthetical change-request tags (CO 525/CO 529) and long compound sentences that slow reading.

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?

With no output schema, the description correctly supplies the return contract (inner result verbatim), the failure modes, and the authorization model. For a meta-dispatch tool of this complexity, an agent has everything needed to call it correctly.

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 already 100%, so the baseline is 3; the description adds conditional meaning (tenant_id required only for branched tools, omitted for root) plus a concrete invocation example and the provenance of valid tool names, which the schema only gestures at.

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) and immediately names the exact client condition it exists for: runtimes that only call tools in their own tools/list. It is clearly distinguished from the sibling catalog/help/enter_tenant tools, which it references as the source of inner tool names and schemas.

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: branched platform tools require tenant_id + tool + arguments, while unlisted root tools take tool + arguments WITHOUT tenant_id. It names the sibling tools that supply names and schemas (federation_enter_tenant, federation_help with tool_defs:all) and points at the prompt family that lives in that unlisted space.

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

All ComOS Federation Gateway toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources