Skip to main content
Glama

federation_enter_tenant

Read-onlyIdempotent

Enter a tenant to receive its tool surface (progressive disclosure). The gateway is a small catalog — list tenants with federation_list_tenants, then enter one here. The reply's platform_tools names the entered platform's REAL action tools (e.g. retail → catalog_search / order_create; bookings → services_search / booking_hold); read a tool's schema with federation_help {"tenant_id":"","tool_defs":""}; composed_tool_defs carries its knowledge tools. Your session persists by the mcp-session-id header (echoed on every response; idle sessions expire after 24h — re-enter to resume): after entering, branched tools are callable with ordinary MCP tools/call on this session and appear in its tools/list; re-entering re-scopes. REST twin: POST /tools/ on this host, JSON body = the tool's arguments plus {"tenant_id":""}, with your Authorization header for scoped tools. Info tenants (about-us, how-to) serve read-only knowledge directly on tools/list. Returns: { platform_tools: [...] } — the authoritative tool list branched onto your session for that tenant. Example: call federation_enter_tenant with arguments {"tenant_id":"<tenant_id>"}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tenant_id": "<tenant_id>"
    },
    "name": "federation_enter_tenant"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesThe tenant id to enter (e.g. "about-us").

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.7/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 substantial context they cannot express: session binding via the mcp-session-id header, a 24h idle expiry and resume-by-re-entering, that branched tools become callable via ordinary tools/call and appear in tools/list, and a REST twin with its argument shape. That is far beyond 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.

Conciseness3/5

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

Purpose is front-loaded in the first clause, but the remainder is a dense single paragraph packing session mechanics, branching semantics, a REST twin, and an example into parenthetical-heavy prose. Almost every fact earns its place, yet the packaging makes it harder to scan than a short structured layout would.

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 carries the return contract itself ('{ platform_tools: [...] }' with its authoritative meaning) and explains the session model, the help path for reading individual schemas, and info tenants' read-only behavior. Nothing material for correct invocation is missing.

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% and only one parameter exists, so baseline is 3; the description still adds meaning by pointing to federation_list_tenants as the source of tenant ids and naming example tenants ('about-us', 'retail'), and by showing the literal argument object. It stops short of documenting tenant-id format or validation beyond the schema's maxLength.

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 — 'Enter a tenant to receive its tool surface' — and implicitly contrasts with federation_list_tenants, which only lists tenants rather than entering one. An agent can immediately tell what this does and how it differs from the catalog-listing sibling.

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?

Gives an explicit sequence: list tenants with federation_list_tenants, then enter one here, and names federation_help as the way to read a tool's schema afterwards. It also states when to re-enter (idle expiry, re-scoping), which is exactly the when/when-again guidance an agent needs.

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.