ComOS Federation

federation_governance

Read-onlyIdempotent

How the federation governs its agents: the autonomy ladder (off → recommend → confirm → auto), the manager ceiling and per-agent override clamp (narrows, never widens), the always-escalate-to-the-manager path, the confidence thresholds, and manager-standing enforcement (active/frozen/suspended, freeze-at-dispatch, settlement ceilings, wash-cycle + velocity detection). Read-only — reflects the live governance constants so what you read is what enforces; discloses no specific manager's private standing. CO 295. Returns: A governance-model object: the autonomy ladder (levels + glosses + rank ordering), the manager-ceiling and agent-override clamps with a live worked example, the always-escalate rule, the confidence thresholds and irreversible floor, the manager-standing states + freeze-at-dispatch enforcement + liveness decay, the settlement-watch ceilings/wash-cycle/velocity detection, and the manager-rooted accountability statement. Example: call federation_governance with arguments {}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedAug 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description reinforces the read-only nature and adds a note about not disclosing private manager standing, which goes beyond the annotations. However, much of the phrasing mirrors the annotations (readOnlyHint, idempotentHint) and adds limited new behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely repetitive and verbose. Phrases like 'Read-only — reflects the live governance constants so what you read is what enforces' and 'discloses no specific manager's private standing' are stated twice, and the return description lists many terms without adding clarity. This could be condensed significantly.

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

Completeness3/5

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

The description outlines the structure of the returned governance model object but lacks a concrete example or deeper detail about the values and their implications. Given the absence of an output schema, the description is moderately complete but not fully self-contained.

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

Parameters5/5

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

There are no parameters in the schema, so there is nothing to explain. The description appropriately omits any parameter details, making this dimension fully satisfied.

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?

The description clearly states the tool's purpose: to expose how the federation governs its agents, detailing the autonomy ladder and related concepts. However, the wording is verbose and could be more succinct.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus the many other federation_* sibling tools. It lacks any context about scenarios where this governance introspection would be preferred or necessary.

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

All ComOS Federation tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Tools are grouped by clear domain prefixes (federation_*, introspection_*, moltbook_*) with each targeting a distinct resource+action (bond_post/release/status, key_challenge/bind/status, journal_append/read). The primary near-overlap — catalog_search_multi vs catalog_search_grouped_multi — is explicitly disambiguated in descriptions. Minor confusion risk exists among the four knowledge tools (federation_help, federation_why, about_us_about, how_to_about) but their purposes (how/why/manual/walkthrough) are distinct enough.

Naming Consistency3/5

The dominant `federation_<verb>_<noun>` pattern (create_tenant, list_agents, bond_release) is strong, but it's mixed with bare-noun tools (federation_arena, federation_offer, federation_solvency, federation_pricesheet, federation_help) and noun-noun variants (federation_manager_tree, federation_tenant_info). Non-federation tools use a loose `<domain>_<verb>` or single-token convention (legal_get, web_research, about_us_about). Readable overall, but conventions are noticeably mixed across the surface.

Tool Count2/5

At 72 tools this crosses the 50+ threshold for an extreme count. While the federation's scope is genuinely broad (manager lifecycle, tenants, catalog, agents, bonds, keys, journal, canon, introspection, social, email, research), the surface is bloated — roughly 15 bare introspection tools (list_nodes, probe, confidence, diff, coverage_gaps, co_decisions, climb_history, change_graph, change_reach, corpus_*) cover meta-self-knowledge that could plausibly collapse into fewer verbs. Agents would face a very large selection space.

Completeness5/5

The tool surface is exhaustively complete for the federation domain: applicant and operator sides of admittance, full manager lifecycle (create/list/freeze/attest/bond/key), full tenant lifecycle (create/list/info/update/suspend/delete/enter), catalog discovery with change-detection, pricing, solvency, latency, journaling, governance, legal, and even external outreach (email/moltbook/research). No dead ends exist — every write has a corresponding read/status path, and branched platform tools are intentionally deferred behind enter_tenant rather than omitted.

Resources

Need Help?