Skip to main content
Glama
safiyu

ctxtest

stat

Check the server status to verify connectivity and health.

Instructions

Check the status of the server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'stat' tool – returns a status message 'running well' when called.
    if (request.params.name === "stat") {
      return {
        content: [
          {
            type: "text",
            text: "running well",
          },
        ],
      };
    }
  • Input schema for the 'stat' tool – defines it with no required parameters.
    {
      name: "stat",
      description: "Check the status of the server",
      inputSchema: {
        type: "object",
        properties: {},
      },
  • src/index.ts:24-51 (registration)
    Registration of the 'stat' tool via ListToolsRequestSchema handler – included in the tool list with name, description, and input schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "hello-world",
            description: "A simple hello world tool",
            inputSchema: {
              type: "object",
              properties: {
                name: {
                  type: "string",
                  description: "The name to say hello to",
                },
              },
              required: ["name"],
            },
          },
          {
            name: "stat",
            description: "Check the status of the server",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
        ],
      };
    });
Behavior2/5

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

No annotations are available, so the description bears full responsibility for behavioral disclosure. It merely states 'Check the status' without detailing what status information is returned (e.g., health, uptime) or any potential side effects. The description lacks depth.

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?

The description is a single sentence without unnecessary words. It is highly concise and front-loaded with the action.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is too minimal. It does not explain what the output looks like or potential error conditions. For a simple status tool, it is adequate but could be improved by briefly noting output format (e.g., plain text, JSON).

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 has zero parameters, so no parameter information is needed. The description adds no meaning beyond the input schema, but per guidelines, 0 parameters yields a baseline of 4.

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 description 'Check the status of the server' clearly identifies the verb (check) and resource (status of the server). It is specific and distinct from the sibling tool 'hello-world', though it does not explicitly differentiate from it.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusion criteria. It only states the action without context.

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/safiyu/ctxnest'

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