Skip to main content
Glama

ComOS Federation

by io.github.ronrey

federation_catalog_search_grouped_multi

Read-onlyIdempotent

Search product FAMILIES (variants of the same product grouped together) across multiple tenants in parallel. Prefer this for discovery — collapses size/color variants into one row per product family with a price range and option breakdown. Use federation_catalog_search_multi when you need exact variant SKUs. tenant_ids come from federation_list_tenants (or pass "all"). Public read — auth_token is optional. Returns: { results: [{ tenant_id, status, data?, error? }], summary: { total_tenants, succeeded, failed } } — per-tenant data is grouped families with priceRange, variantCount, options, and nested variants. Example: call federation_catalog_search_grouped_multi with arguments {"tenant_ids":"","query":""}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum variants to fetch per tenant before grouping (default 50, max 250)
queryYesSearch query string
categoryNoFilter by category
auth_tokenNoOptional JWT auth token
tenant_idsYesArray of tenant IDs to search, or "all" for all active tenants

Schema Changelog

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

  1. Changed3 schema fields changed
    • addedInput schema / properties / auth_token / maxLength
      Added value: +4000
    • addedInput schema / properties / category / maxLength
      Added value: +4000
    • addedInput schema / properties / query / maxLength
      Added value: +4000
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive. The description adds valuable context: 'Public read — auth_token is optional', describes grouping behavior (collapses variants, price range, options), and details the return structure. No contradictions.

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 a single paragraph but well-structured: purpose, usage preference, tenant source, read state, return format, and example. Every sentence adds value, though it could be slightly more concise; still appropriately sized for a tool with no output schema.

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?

There is no output schema, so the description carries the full burden of explaining returns. It fully describes the return structure, per-tenant data, and provides an example call. It also covers all required and optional parameters, making it complete for an agent to select and invoke 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% with parameter descriptions, so baseline is 3. The description adds value by explaining tenant_ids come from federation_list_tenants, and clarifies the 'limit' parameter's role in grouping (max variants fetched before grouping). This goes beyond schema alone.

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?

Clearly states it searches product families across multiple tenants, explicitly distinguishing from sibling federation_catalog_search_multi which returns exact variant SKUs. The verb 'search' and resource 'product families' are specific.

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 says 'Prefer this for discovery' and instructs to use federation_catalog_search_multi when exact variant SKUs are needed. Also notes tenant_ids come from federation_list_tenants or 'all', providing clear when-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 toolsInspect
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