Skip to main content
Glama

Physical Capability Cloud

get_subnet_status

Read-only

The gateway's agent bridge status: whether its in-process agents started, their names and roles, and the bridge's conversation and recent-message counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value by disclosing the content of the response (agent start state, names, roles, counts), but says nothing about freshness, caching, or behavior when no bridge is running.

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?

One sentence, with the subject and the most important fact (whether agents started) placed first, followed by the secondary detail. The colon-and-list construction is slightly dense but every clause identifies a distinct returned field, so nothing is wasted.

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 no parameters and no output schema, the description must carry the return-value burden, and it does so by enumerating the reported fields. The only shortfall is that it never reconciles the 'subnet' in the tool name with the 'agent bridge' subject, leaving a small ambiguity about scope.

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?

The tool takes zero parameters and the schema is empty, so there is no parameter meaning to convey; the baseline for a 0-param tool applies. The description correctly implies the call is argument-free by describing a single implicit target.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (the gateway's agent bridge) and enumerates exactly what is reported: agent start state, agent names and roles, conversation count, recent-message count. That is far more specific than the sibling status tools, though the tool name 'get_subnet_status' does not align with the 'agent bridge' subject, which introduces slight ambiguity for an agent scanning by name.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no named alternatives among the many sibling status tools (get_operator_status, get_verification_status, get_settlement_status, etc.). The agent must infer from the returned-field list whether this is the right status tool to call.

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.