Skip to main content
Glama

Get Live Switchboard Health & Pool Telemetry

get_switchboard_telemetry
Read-onlyIdempotent

Return global US-EAST4 switchboard health, Grade A/B/D/E/F pool counts, autonomous registry crawl cursor state, and external hook telemetry. Use for system-wide status and pool metrics; use get_agent_dossier for an individual agent.

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": "get_switchboard_telemetry"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_recent_activityNoPublic privacy protection strips raw caller User-Agent/IP entries by default (default false); only recent_activity_count is returned publicly.

Output Schema

NameRequiredDescriptionDefault
statusYesService operational state ('ok').
spec_versionYesActive Radial Switchboard specification revision.
live_callable_abYesCount of live verified Grade A and Grade B endpoints.
total_unsorted_poolYesTotal indexed MCP and A2A records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include_recent_activity / description
      Previous value: -"When false, omits the 25-item recent_activity caller array for a compact payload (default true)."New value: +"Public privacy protection strips raw caller User-Agent/IP entries by default (default false); only recent_activity_count is returned publicly."
  2. Changed2 schema fields changed
    • changedInput schema / properties / include_recent_activity / description
      Previous value: -"Optional flag (default true) indicating whether to include the rolling 25-event external hook and crawler activity feed in the response."New value: +"When false, omits the 25-item recent_activity caller array for a compact payload (default true)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "live_callable_ab": {
      +      "description": "Count of live verified Grade A and Grade B endpoints.",
      +      "type": "integer"
      +    },
      +    "spec_version": {
      +      "description": "Active Radial Switchboard specification revision.",
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "Service operational state ('ok').",
      +      "type": "string"
      +    },
      +    "total_unsorted_pool": {
      +      "description": "Total indexed MCP and A2A records.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "spec_version",
      +    "total_unsorted_pool",
      +    "live_callable_ab"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / include_recent_activity
      Added value: +{
      +  "description": "Optional flag (default true) indicating whether to include the rolling 25-event external hook and crawler activity feed in the response.",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by enumerating what the response covers (health, pool grade distribution, crawl cursor state, hook telemetry) and by scoping the output as global US-EAST4. It does not note freshness or snapshot timing, which keeps it below a 5.

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

Conciseness5/5

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

Two sentences, both front-loaded with the substantive content first and the routing hint second. No filler, no restatement of the tool name, and every clause names concrete returned data.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, full annotation coverage, and complete parameter documentation, the definition is nearly self-sufficient. The only gap for a "live" telemetry tool is the absence of any statement about freshness, caching, or refresh cadence, which an agent might need when deciding how often to call it.

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?

There is only one optional parameter and schema description coverage is 100%, so the schema already explains include_recent_activity and its privacy stripping in detail. The description adds no further meaning about the parameter, which is the expected baseline 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?

Uses a specific verb ("Return") with a precisely enumerated resource set: switchboard health, Grade A/B/D/E/F pool counts, registry crawl cursor state, and external hook telemetry. It also names the sibling get_agent_dossier for per-agent data, so an agent can distinguish the aggregate view from the individual view 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 Guidelines4/5

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

"Use for system-wide status and pool metrics" states the intended context, and the follow-up sentence routes to get_agent_dossier for individual agents. That is a clear when-to-use plus a genuine alternative, but no explicit exclusions (e.g., historical versus live, or when not to poll) are given.

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.