Skip to main content
Glama

federation_catalog_platforms

Read-onlyIdempotent

Browse the ComOS network's composable platforms and presets. preset: "" answers one preset's row alone: its build (whether federation_create_tenant builds it here) and create_with (its inputs and an example call). Presets built from preset_inputs: campground, equipment-delivery, events, fitness, food, lodging, salon, travel-agency, travel-portal, venue. Without preset, every platform and every preset row (a recipe composed by hand is one too); presets never count in summary.total (CO 455). side="vendor": platforms you SELL ON (retail, bookings, services, …); side="customer": tools you RUN WITH (messaging, shipping, marketing, …). parent="" descends into a platform's sub-catalog (parent="messaging": email, sms, dm). Pairs with federation_catalog_agents: the operators you hire to run what you become.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "federation_catalog_platforms"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNoFilter to sell-on (vendor) or run-it (customer) platforms. Omit for all platforms.
parentNoDescend 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.
presetNoOne preset's row alone (build, inputs, an example call); side and parent are ignored. The keys are in this tool's description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / preset
      Added value: +{
      +  "description": "One preset's row alone (build, inputs, an example call); side and parent are ignored. The keys are in this tool's description.",
      +  "maxLength": 64,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / parent / maxLength
      Added value: +4000
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, but the description adds substantial extra context: preset mode returns build/create_with details and an example call, unspecific browsing returns platform and preset rows, presets never count toward summary.total, and side is ignored when parent or preset is supplied. These are concrete behavioral details an agent would otherwise have to discover by trial.

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 front-loaded with the overall purpose and then walks through the three modes in a logical order. It is somewhat dense and includes awkward phrases like 'answers one preset's row alone' and an unexplained '(CO 455)', but most sentences carry useful information and there is no major 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?

For a read-only catalog browser with no output schema, the description is complete enough to use correctly: it explains the two top-level browsing modes, the preset lookup mode, the meaning of both side values, the parent descent behavior, and a notable summary.total counting rule. It does not describe pagination or the full response shape, but those gaps are not clearly necessary for an agent to choose and invoke this tool.

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?

Even with 100% schema coverage, the description adds meaning beyond the schema by listing the preset keys, explaining that side='vendor' means platforms you SELL ON versus side='customer' meaning tools you RUN WITH, and giving a concrete parent='messaging' example. It also clarifies parameter interactions such as side being ignored when parent or preset is present.

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 states a specific verb ('Browse') and resource ('ComOS network's composable platforms and presets'), then immediately distinguishes the three operating modes: preset row lookup, full platform/preset listing, and filtered browsing by side or parent. This is far more than a restatement of the name and gives an agent a clear picture of what the tool returns.

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

Usage Guidelines4/5

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

It explains when to use preset versus no preset, what side='vendor' and side='customer' mean in practice, and how parent descends into sub-catalogs. It also says it pairs with federation_catalog_agents, giving useful context, but it does not explicitly exclude or compare against other sibling catalog/search tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources