Skip to main content
Glama
Example MCP Server

Example MCP Server

by Ranjith63812

system_info

Retrieves operating system, memory, CPU, and Node.js version details to help diagnose platform and runtime environment.

Instructions

Returns system and platform information (OS type, memory, CPU, Node.js version)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the return fields, which implies a read-only informational call, but never explicitly states that it has no side effects, requires no permissions, or is cheap/fast. It also does not say whether the information describes the local host, the server process, or a remote environment.

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 front-loaded sentence with the resource named first and the returned fields parenthesized. No filler, no redundancy.

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 simple no-argument informational tool with no output schema, the description is nearly sufficient because it enumerates the fields returned. It stops short of indicating the shape or units of the response (e.g., bytes vs GB for memory), which is the only material gap.

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 for the description to disambiguate; the baseline for parameter-free tools applies. The description correctly implies a no-argument call.

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?

States a specific verb ('Returns') and resource ('system and platform information') and enumerates the concrete fields (OS type, memory, CPU, Node.js version), so an agent knows exactly what the call yields. It does not distinguish itself from siblings, but the siblings given (file_reader, git_status, ping) have no apparent overlap, so the ambiguity cost is low.

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?

There is no when-to-use guidance at all: nothing says to call this for diagnostics, environment checks, or capability probing, and nothing states when it is unnecessary. Usage is only weakly implied by the content of the return values.

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

Deploy Server

Other Tools