io.github.olzhas-raiganiyev/goszakup-mcp

Server status

server_status

Read-onlyIdempotent

Check the server version and confirm whether procurement data is mock or live so you can validate the environment before relying on query results.

Instructions

Report the server version and whether it serves mock or live procurement data.

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": "server_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`name`	Yes
`version`	Yes
`data_source`	Yes	'mock' (offline sample data) or 'ows' (official live API).
`token_configured`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value beyond that by naming the two facts returned, especially the mock-vs-live distinction, which warns the agent that downstream data may be synthetic. It stops short of saying anything about cost, latency, or side effects, but for a zero-param read-only probe that is a minor gap.

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 sentence with no filler, and the most decision-relevant fact (mock vs live) is stated up front alongside the version. Nothing is redundant or padded.

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

Completeness5/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 status tool with an output schema present, the description covers everything the agent needs: what it reports and why it matters. Return-value formatting is handled by the output schema, so no further detail is required.

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 no parameters, so the baseline of 4 applies. The empty schema is fully consistent with the description, which implies a self-contained query requiring no caller input.

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?

The description pairs a specific verb ("Report") with a specific resource (server version and mock-vs-live data mode), which is exactly what the tool name implies but stated concretely. An agent can tell at a glance that this is a diagnostic/introspection call rather than a data query, distinguishing it from the sibling check_bin.

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 or when-not-to-use statement, no mention of calling it before relying on results. The usage is strongly implied - you call it to learn the server version or whether data is mock - but an agent must infer the timing (e.g., call first to check if data is synthetic).

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

Deploy Server