Skip to main content
Glama

get_network_status

Queries the Matrix Compute discovery relay for live GPU worker availability, total VRAM capacity, confidential computing (TEE) enclaves, and sats_per_gflop pricing.

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

Input Schema

NameRequiredDescriptionDefault
min_vram_mbNoMinimum worker VRAM filter in MB (optional).
max_price_per_gflopNoMaximum worker price filter in satoshis per GFLOP (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It implies read-only through "Queries" and discloses that results are live (real-time relay state), but says nothing about response shape, latency, freshness guarantees, rate limits, or whether pricing/availability data can be stale. For an unannotated tool this leaves meaningful gaps.

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?

A single dense sentence with the data source front-loaded and the returned dimensions following. No filler, no repetition of the tool name, and every clause conveys distinct information.

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

Completeness3/5

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

The description covers the data source and what categories of information come back, which is the core need for a two-optional-parameter read tool. However, with no output schema and no annotations, it never describes the response structure (e.g., whether a list of workers with per-worker pricing is returned), leaving the agent to discover that at call time.

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 description coverage is 100%, so both optional filters (min_vram_mb, max_price_per_gflop) are already documented in the schema. The description reinforces the sats_per_gflop unit of the price filter but does not explain filter interaction or defaults, so it adds little beyond the schema.

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 pairs the specific verb "Queries" with a named resource ("Matrix Compute discovery relay") and enumerates what it surfaces: live GPU worker availability, VRAM capacity, TEE enclaves, and sats_per_gflop pricing. That is enough to tell it apart from siblings like estimate_job_cost or execute_distributed_matmul, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

There is no explicit when-to-use statement, no exclusion, and no named alternative. Usage is only implied by the phrase "live GPU worker availability," which suggests a discovery step preceding job execution or cost estimation. An agent can infer the role but gets no routing help.

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.