Skip to main content
Glama
Sign In
teaching-mcp-server

teaching-mcp-server

by DouglasGBailey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get local system information

get_system_info

Get operating system, CPU, memory, uptime, and current local time to diagnose the host or tailor environment-aware suggestions.

Instructions

Report information about the machine running this MCP server: operating system, CPU, memory, uptime, and current local time. Useful for diagnostics or environment-aware suggestions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. The verb 'Report' implies a non-mutating read with no side effects, which is the key behavioral trait, but it says nothing about permission requirements, whether values are live or cached, or any rate/cost considerations.

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, zero filler; the scope (what is reported) is front-loaded and the use case follows. Every clause earns its place.

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?

There is no output schema, and the description compensates well by enumerating the returned fields (OS, CPU, memory, uptime, local time) so an agent knows what to expect. The only gap is that it doesn't specify the format or units of the returned values.

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 there is nothing to document and the baseline of 4 applies. The description correctly does not invent parameter semantics.

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 names a specific action ('Report information about the machine running this MCP server') and enumerates the resources returned (OS, CPU, memory, uptime, local time). This is unambiguous and cannot be confused with any sibling such as read_file or get_note.

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?

It offers a usage context ('useful for diagnostics or environment-aware suggestions') but does not state when to prefer this over any alternative or any preconditions. With zero parameters and no competing sibling, this is adequate implied guidance rather than explicit routing.

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