Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_status

Check POHODA mServer status to verify readiness for requests by monitoring queue count, server state, and address.

Instructions

Get POHODA mServer status: processing queue count, server state (idle/working), and server address. Use to check if the server is ready to accept requests.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and implementation of the pohoda_status tool handler.
    server.tool(
      "pohoda_status",
      "Get POHODA mServer status: processing queue count, server state (idle/working), and server address. Use to check if the server is ready to accept requests.",
      {},
      async () => {
        try {
          const xml = await client.getStatus();
          const data = parseStatusXml(xml);
          const lines: string[] = [];
          if (data.processing != null) lines.push(`Processing queue: ${data.processing}`);
          if (data.status != null) lines.push(`Server status: ${data.status}`);
          if (data.server != null) lines.push(`Address: ${data.server}`);
          if (data.message) lines.push(`Message: ${data.message}`);
          return ok(lines.length > 0 ? lines.join("\n") : xml);
        } catch (e) {
          return err((e as Error).message);
        }
      }
    );
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses what specific information is returned (queue count, idle/working state, address) and implies read-only behavior via 'Get'. However, it omits explicit safety guarantees, idempotency, or error states that would be helpful for a server status tool.

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 well-structured sentences: first defines the operation and return payload, second defines usage context. No redundant words or unnecessary verbosity. Information is front-loaded and immediately actionable.

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 tool without output schema, the description adequately compensates by enumerating the three specific status fields returned (queue, state, address). Sufficient for tool selection, though an output schema would provide better completeness.

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?

Tool has 0 parameters with 100% schema coverage (trivially). Per rubric, 0 params = baseline 4. Description appropriately does not invent parameters, focusing instead on return value semantics.

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?

Description uses specific verb 'Get' with clear resource 'POHODA mServer status' and distinguishes from siblings by focusing on server health rather than business data (unlike the many create/list/update tools). It further clarifies by listing specific returned data points (queue count, state, address).

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?

Explicitly states when to use: 'Use to check if the server is ready to accept requests.' This clearly positions it as a prerequisite health-check tool. Lacks explicit 'when-not-to-use' or named alternatives, but effectively conveys its role as a readiness probe.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hlebtkachenko/pohoda-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server