ComOS Federation Gateway

federation_catalog_platforms

Read-onlyIdempotent

Browse the ComOS network's composable platforms as a recursive catalog. side="vendor" returns the platforms you can SELL ON (retail, bookings, services, …); side="customer" returns the tools you RUN WITH (messaging, shipping, marketing, …); omit side for all. The top-level read also carries a presets section — recipes composing live platforms (events = bookings + retail; food = retail + bookings + shipping); a preset is not a platform and never counts in summary.total (CO 455). parent="" descends into a platform's sub-catalog — e.g. parent="messaging" returns its channels (email, sms, dm). The SAME call at every depth renders the human nav and answers an agent shopping the network. Pairs with federation_catalog_agents: platforms are what you become; agents are the operators you hire to run them. Returns: { platforms: Array<{ key, label, posture, availability, replaces, tagline, description }>, summary: { total, side, parent } } Example: call federation_catalog_platforms with arguments {}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`side`	No	Filter to sell-on (vendor) or run-it (customer) platforms. Omit for all platforms.
`parent`	No	Descend into a platform's sub-catalog (e.g. parent="messaging" → email/sms/dm). Omit for the top-level platform list. When present, side is ignored.

Schema Changelog

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

Changed1 schema field changedAug 20, 2026
- addedInput schema / properties / parent / maxLength
```
Added value: +4000
```
First observedAug 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds context beyond that: 'a preset is not a platform and never counts in summary.total (CO 455),' plus the side and parent interplay ('When present, side is ignored'). This enriches behavioral understanding well past annotation coverage.

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?

The description is dense and information-rich, front-loaded with the main purpose and ending with an example. Every sentence contributes value, though it is somewhat long; however, given the tool's complexity, the length is justified and there is no redundancy.

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 fully specifies the return shape: '{ platforms: Array<{ key, label, posture, availability, replaces, tagline, description }>, summary: { total, side, parent } }'. It also explains recursive descent, presets, and side semantics, making it complete for an agent to use 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 100% for both parameters, but the description adds practical examples (vendor: retail/bookings; customer: messaging/shipping) and clarifies the top-level vs. parent behavior more concretely. This goes slightly beyond the schema's own descriptions, so a 4 is warranted.

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?

The description uses the specific verb 'Browse' with a clear resource ('the ComOS network's composable platforms') and characterizes it as a 'recursive catalog.' It differentiates from siblings by contrasting platforms with agents: 'platforms are what you become; agents are the operators you hire to run them.'

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?

Explicitly states when to use this tool: 'answers an agent shopping the network' and 'renders the human nav.' It names an alternative, federation_catalog_agents, and explains the division of responsibility, giving clear when-to-use vs. when-not-to-use guidance.

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 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

Most tools have clearly distinct purposes with detailed descriptions. A few pairs like federation_catalog_search_multi and federation_catalog_search_grouped_multi could be confused, but descriptions explicitly delineate when to use each. Overall, the boundaries are clear.

Naming Consistency3/5

The federation_* tools follow a consistent verb_noun pattern, but many tools use other prefixes (introspection_, moltbook_, llm_, web_, cohort_, legal_, about_us_, how_to_), breaking overall consistency. Within the main federation domain naming is predictable, but across the full set it's mixed.

Tool Count2/5

72 tools is far beyond the typical 3-15 for a coherent set. While the federation scope is broad, the sheer number makes the surface unwieldy and increases the risk of misselection, even if each tool individually earns its place.

Completeness4/5

The tool surface covers lifecycle management (create/update/delete/suspend tenants), manager operations, agents, catalog search, governance, introspection, legal, and auxiliary functions like email and web research. Platform-specific actions are exposed via federation_enter_tenant, so no critical dead ends are apparent.

Resources

Need Help?