Skip to main content
Glama
Sign In
Agent Action Gateway

Agent Action Gateway

by alinejad-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Ping

ping
Read-only

Checks gateway health by returning "pong" and optionally echoing a short message, confirming the MCP server is reachable.

Instructions

Health check. Returns "pong", optionally echoing a short message.

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 text to echo back

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds the return contract (the literal string "pong") and the fact that echoing is conditional. It does not say what a failing health check looks like or whether it probes downstream dependencies, which is the remaining gap.

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 short sentences, return behavior front-loaded, zero filler. Every clause carries information the agent needs.

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 single-optional-parameter, no-output-schema tool, the description covers purpose, input effect, and return value. The only ambiguity is scope of "health" — the MCP server itself versus dependencies — which is minor for a ping.

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?

Schema coverage is 100% and the parameter already carries "Optional text to echo back" plus a maxLength constraint. The description's "optionally echoing a short message" restates that meaning rather than adding syntax or behavior beyond the schema; baseline 3 applies.

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 states a concrete operation ("Health check") and its exact output ("Returns \"pong\""), plus the conditional echo. That is enough for an agent to distinguish it instantly from get_order and search_orders, which are data-retrieval tools.

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?

Usage is only implied by the label "Health check" — an agent can infer it is for connectivity/liveness verification. There is no explicit when-to-use or when-not-to-use statement, though the unrelated siblings make misselection unlikely.

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