Skip to main content
Glama

federation_offer

Read-onlyIdempotent

For an agent that wants to SELL on ComOS: read the network's vendor offer — public and read-only, no token needed. Not for buying: to buy, enter the store with federation_enter_tenant. Returns the machine-legible offer (what you get and what it costs) plus the exact steps to apply: obtain an OAuth token (self-service, any OAuth login, no human review), then call federation_apply with it. This tool changes nothing; it is the door's window, and federation_apply is the door; calling federation_apply accepts the ComOS Terms of Service. Cost: Free to join and operate. No subscription, no seat, no minimum, no trial. 3% when a sale settles. A card sale also pays the card processor's fee (2.9% + $0.30), passed through at cost. Some acts are priced in Coms (1 Com = $0.01), most after a free allowance; an act that is not on the sheet is free. The sheet is the federation_pricesheet tool: free, no token. 6% on top when you buy Coms. Buying them by card adds the same processor fee. Returns: { offer: <vendor manifest — the same document as /.well-known/comos-vendor.json>, how_to_apply: { step_1, step_2, note } } Example: call federation_offer with arguments {}.

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_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoOptional: where you found us (e.g. moltbook, registry:mcp.so, direct). Arrival telemetry only — the offer content never varies by channel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / channel / maxLength
      Added value: +4000
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds material context beyond them: no token required, self-service OAuth with no human review, the fact that accepting terms happens in federation_apply rather than here, and a full cost model (3% settlement, pass-through processor fee, Com pricing). Some of this lightly echoes the readOnly hint, but the auth and consent disclosures are genuinely additive.

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

Conciseness3/5

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

Purpose and the sibling exclusion are correctly front-loaded in the first two sentences, but the body sprawls into Com pricing and a 6% surcharge on buying Coms, which the description itself says belongs to federation_pricesheet. That digression dilutes the read path an agent actually needs.

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 supplies the return shape ({ offer, how_to_apply: { step_1, step_2, note } }) and explains what the offer document is (the vendor manifest). It also names the file it mirrors and the apply path, which is everything needed to call and use the result.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter 'channel' is fully documented in the schema as arrival telemetry. The description never mentions it, adding no meaning beyond the schema, though the 'call with arguments {}' example implicitly signals it is optional. Baseline 3 applies when the schema does the work.

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 and resource — 'read the network's vendor offer' — plus its access mode (public, read-only, no token). It explicitly carves itself away from the buying path by naming federation_enter_tenant, so an agent can separate the two without opening either schema.

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 audience ('for an agent that wants to SELL on ComOS'), explicit exclusion ('Not for buying: to buy, enter the store with federation_enter_tenant'), and the downstream path is spelled out (get OAuth token, then call federation_apply). The free, no-token pricesheet alternative is also named.

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