Skip to main content
Glama
saurabh-sde3

common_mcp

by saurabh-sde3

get_basic_details

Retrieve system information including platform, Node version, architecture, current time, and uptime. Optionally include hostname.

Instructions

Returns basic system and runtime details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeHostnameNo

Implementation Reference

  • server.js:13-43 (registration)
    Registration of the 'get_basic_details' tool via server.registerTool().
    server.registerTool(
      "get_basic_details",
      {
        description: "Returns basic system and runtime details.",
        inputSchema: {
          includeHostname: z.boolean().optional()
        }
      },
      async ({ includeHostname }) => {
        const details = {
          platform: process.platform,
          nodeVersion: process.version,
          architecture: process.arch,
          currentTimeIso: new Date().toISOString(),
          uptimeSeconds: Math.floor(process.uptime())
        };
    
        if (includeHostname) {
          details.hostname = os.hostname();
        }
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(details, null, 2)
            }
          ]
        };
      }
    );
  • Input schema defining the optional 'includeHostname' boolean parameter.
    {
      description: "Returns basic system and runtime details.",
      inputSchema: {
        includeHostname: z.boolean().optional()
      }
  • server.js:21-42 (handler)
    The async handler function that collects platform, Node version, architecture, current time, and optionally hostname, then returns them as JSON.
    async ({ includeHostname }) => {
      const details = {
        platform: process.platform,
        nodeVersion: process.version,
        architecture: process.arch,
        currentTimeIso: new Date().toISOString(),
        uptimeSeconds: Math.floor(process.uptime())
      };
    
      if (includeHostname) {
        details.hostname = os.hostname();
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(details, null, 2)
          }
        ]
      };
    }
Behavior2/5

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

No annotations provided, so description must cover behavior. It only says 'returns' but does not disclose read-only nature, side effects, or any potential costs. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, very concise. But lacks structure; no additional details or sections. Adequate for a simple tool but not well-structured.

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

Completeness2/5

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

Given simplicity (1 optional param, no output schema), description should still explain what 'basic system and runtime details' includes and what the return looks like. Incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and description does not mention the 'includeHostname' parameter. No added meaning beyond what schema provides (which is just type boolean). Fails to compensate for low coverage.

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?

Description clearly states verb 'returns' and resource 'basic system and runtime details', which is a clear purpose. No siblings exist to differentiate, so no issue with distinction.

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?

No guidance on when to use this tool versus alternatives. Since there are no siblings, some implied usage, but no explicit context or exclusions.

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/saurabh-sde3/common_mcp'

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