VeriTeknik

Check monitored service status

check_service_status

Read-onlyIdempotent

Returns the up/down status of the connected company's monitored VPS servers and domains: 24-hour uptime, for domains the SSL certificate days remaining, and for every entry lastCheck plus lastCheckAgeSeconds. An entry whose last check is older than 30 minutes has status stale, uptime24h null and its last known state in lastKnownStatus - treat it as unknown, not as up. Returns an empty list when no monitoring is configured; never returns a fabricated healthy status. No parameters needed. Call it when the user asks whether something is up or down right now, rather than what they own.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description layers on real operational semantics: stale entries after 30 minutes, uptime24h forced to null, last known state surfaced in lastKnownStatus, and an explicit instruction to treat stale as unknown rather than up. It also warns that an empty list means no monitoring is configured and that a fabricated healthy status is never returned - none of which the annotations convey.

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?

Front-loads what is returned, then the stale/unknown rule, then the empty-list caveat, then the call condition. Dense but every sentence carries unique decision value; the returned-field enumeration is slightly heavy but justified by the stale-handling logic that depends on those fields.

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?

Despite an output schema existing, the description goes further by explaining how to interpret the response fields (stale, uptime24h null, lastKnownStatus, empty list). Combined with the read-only annotations and zero-parameter schema, an agent has everything needed to call and interpret it correctly.

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 zero parameters, so there is nothing to disambiguate beyond confirming 'No parameters needed.' The baseline for a parameterless tool applies.

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?

States a specific verb and resource ('Returns the up/down status of the connected company's monitored VPS servers and domains') and explicitly scopes itself against ownership-listing siblings ('rather than what they own'). An agent can separate it from list_my_domains, list_vps, and the per-resource monitor tools.

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?

Gives an explicit trigger ('Call it when the user asks whether something is up or down right now') plus an exclusion against ownership-listing tools. It does not name the near-neighbor siblings get_vps_monitor_status and get_domain_monitor_status, which it partially overlaps, so the routing guidance stops just short of complete.

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

All VeriTeknik tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.