Skip to main content
Glama

Agent liveness

agent_liveness
Read-onlyIdempotent

Whether one listed agent kept answering the hub's checks: uptime over 7, 30 and 90 days, daily tallies, and every change of state (went dark, came back, retired) with the error behind it. Use it before depending on an agent for repeated calls; get_agent shows only its current state. Read-only, no account. Returns the uptime figures, the daily tallies and the list of changes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agentId": "<agentId>"
    },
    "name": "agent_liveness"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesThe listing id search_agents or get_agent returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agentId / description
      Added value: +"The listing id search_agents or get_agent returned"
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds that no account is required and that state changes are reported with the error behind them, which is genuine behavioral context. It stops short of details like retention limits beyond 90 days or how many daily tallies come back, so it is not fully exhaustive.

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

Conciseness4/5

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

The return contents are front-loaded and the guidance follows immediately, with no filler sentences. The opening is a grammatical fragment ('Whether one listed agent kept answering...'), which slightly slows parsing but costs no real information.

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?

With a single richly-described parameter and no output schema, the description carries the return-value burden and does so by naming the uptime figures, tallies and change list. Minor omissions such as result volume or ordering keep it from being fully complete.

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?

There is one parameter with 100% schema coverage, and the schema already explains that it is a listing id returned by search_agents or get_agent. The description's phrase 'one listed agent' reinforces the cardinality but adds no format, validation or error-handling meaning beyond the schema, so the 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 names a specific resource and metric — an agent's answerability to the hub's checks — and enumerates the contents: uptime over 7/30/90 days, daily tallies, and state transitions with the underlying error. It explicitly separates itself from get_agent, which 'shows only its current state,' so an agent can distinguish the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the operational trigger directly: 'Use it before depending on an agent for repeated calls,' and names the alternative (get_agent) plus why it is insufficient for this purpose. That is explicit when-to-use plus an explicit alternative, which is the top of the scale.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.