Skip to main content
Glama

Get Status

get_status
Read-only

Report what this server can do: it is not connected to a running Fyug and cannot play audio. The result carries the URL for installing Fyug locally.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds real value beyond it: it discloses the negative state (not connected, cannot play audio) and states what the result carries (the install URL). That pre-empts a failed play_preview call. It stops short of describing any other fields the response might contain.

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 short sentences, front-loaded with the capability statement and immediately qualified by the limitation and the payload. No filler, nothing repeated from structured fields.

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?

For a zero-parameter, read-only probe, this covers the essentials: what it reports, the current limitation, and one known return value. With no output schema, a fuller enumeration of returned fields would improve it, but nothing critical is missing for correct invocation.

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?

Zero parameters, so there is nothing to document and no schema gap to compensate for; the baseline of 4 applies. The description correctly adds no invented parameter detail.

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 verb is somewhat generic ("Report what this server can do"), but the follow-up narrows it concretely: it reports that Fyug is not running, that audio cannot be played, and that an install URL is returned. That is specific enough for an agent to know this is a capability/connection-status probe rather than a content-description tool like the describe_* siblings.

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 explicit statement of when to call this versus describe_module or play_preview, no prerequisites, and no exclusions. The only usable cue is indirect: if the agent needs audio playback, the description warns it is unavailable, but the agent has to infer that this tool is the way to check.

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.

Resources