Skip to main content
Glama

mcp-rs status

mcp_rs_status
Read-only

Displays the MCP server's version, mode, protocol version, config file, log and audit log paths, and handler/plugin states. Use it to check the installed version or locate log files.

Instructions

Show the status of the mcp-rs server itself: version, mode, protocol version, config file, where the log and audit log are written, and the state of each handler and plugin. Use it to check the installed version or to find the log files.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known; the description adds the concrete content set the call returns (config path, log paths, handler/plugin state), which is the main behavioral value here. It adds no notes on permissions, cost, or format of the returned status block, so it goes beyond annotations without fully characterizing the response.

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 sentences, both front-loaded: the first defines the resource and its returned fields, the second gives the use cases. No filler, no restatement of the title, and the enumeration is compact rather than padded.

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 no-param, read-only status tool with no output schema, the description does the necessary work by listing the data categories returned, so an agent knows what it will get. It does not describe the shape or format of that status output, which is the one remaining gap given no output schema exists.

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 the baseline is 4 and there is no parameter meaning for the description to add or omit. Nothing here misleads about inputs.

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 ('Show the status of the mcp-rs server itself') and then enumerates exactly what status means: version, mode, protocol version, config file, log/audit log locations, handler and plugin state. There are no siblings to differentiate against, and an agent can predict the payload from the description alone.

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 names two triggering scenarios: checking the installed version and locating the log files. That is clear when-to-use guidance. It stops short of a 5 because there are no exclusions or prerequisites mentioned (e.g., no note that it reflects the running server rather than an on-disk install), though with zero siblings there is little routing ambiguity to resolve.

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