Skip to main content
Glama

Get Status

get_status

Check server status to confirm today's enabled health-data sources, reachability, cache age, and profile presence before running analyses.

Instructions

Server status: today, enabled sources, reachability, cache age and profile presence.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the contents of the report, including cache age and reachability, which hint that results may be stale. What it does not state is that this is strictly read-only, whether it triggers any refresh, or how stale cache is reported. It is a helpful content sketch rather than a full behavioral disclosure, but the zero-parameter, read-oriented shape limits the risk.

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?

It is a single front-loaded fragment with no filler words; every listed item corresponds to something the agent gets back. It is arguably too compressed, since terms like 'today' and 'profile presence' are never unpacked, but there is no wasted wording.

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?

An output schema is present, so the description does not need to explain return values, and with zero parameters there is nothing else to document on the input side. For a simple, parameterless status probe the definition is close to sufficient, with the only gap being the unstated read-only guarantee and the meaning of 'today'.

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?

The tool takes zero parameters, so the baseline is 4, but the description offers nothing about scope control because there is none to control. The only semantic it could have added, such as what 'today' is anchored to (server timezone versus client date), is left unstated. The fragment 'today' is itself ambiguous and the description does not resolve it.

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 the resource ("Server status") and enumerates the five things the report covers: today, enabled sources, reachability, cache age, and profile presence. An agent can tell this is a diagnostic/status read rather than an analytics query like get_lifting_summary. It stops short of contrasting itself with get_overview, which is the nearest ambiguous sibling, so it is clear but not fully differentiated.

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 guidance on when to call this versus alternatives such as get_overview or refresh_cache, and no stated preconditions. The only weak signal is that 'cache age' and 'reachability' imply a diagnostic use case, but that must be inferred. The agent is left to figure out the routing decision on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.