Skip to main content
Glama
Sign In
Agentic MCP Server

Agentic MCP Server

by lucastl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ping

Verify connectivity between the AI agent and the local environment by sending a test signal and receiving an acknowledgment with a timestamp. Optionally include a message to be echoed back.

Instructions

Responds with a pong acknowledgement and timestamp to verify connectivity.

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

Input Schema

NameRequiredDescriptionDefault
messageNoOptional message echoed back with the pong response.

Output Schema

NameRequiredDescriptionDefault
okYes
responseYes
receivedAtYesISO-8601 timestamp indicating when the request was processed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states the response behavior (pong acknowledgement and timestamp) and the purpose, which is sufficient for a non-destructive ping utility.

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, front-loaded sentence with no wasted words. It states the outcome and the purpose efficiently.

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

Completeness5/5

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

This is a very simple tool with one optional parameter and an output schema available. The description, combined with the schema, provides everything an agent needs to invoke it correctly and interpret the basic response.

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

Parameters3/5

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

The schema has 100% description coverage for the only parameter (message), stating it is echoed back with the pong response. The tool description adds no parameter-level detail, but it does not need to because the schema fully documents it.

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 uses a specific verb ('Responds'), identifies the resource ('pong acknowledgement and timestamp'), and states the purpose ('verify connectivity'). It is distinct from all sibling tools, none of which are connectivity checks.

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?

The description clearly implies the tool should be used to verify connectivity or availability, which is adequate context for such a simple utility. No explicit exclusions or alternatives are needed since no sibling tool provides an overlapping function.

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