Skip to main content
Glama

how_is_service

Retrieve a service's health status, telemetry outputs, monitoring coverage and watchers, last check time, and incidents by name; unknown names return available services.

Instructions

How one service is doing, as its page shows it: its state in words, what it sends (logs, metrics, traces, deploys), whether it is watched and by whom, when it was last checked, its incidents and what the cell cannot see about it. service is its name. An unknown name answers with the services there are.

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": {
      "service": "<service>"
    },
    "name": "how_is_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a solid job: it discloses the shape of the response (state, signals, watchers, last check, incidents, unknown blind spots) and explicitly states the edge-case behavior that an unknown name returns the list of available services. It does not mention permission requirements, rate limits, or whether the call has side effects, but 'how is it doing' reasonably implies a read.

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?

Purpose is front-loaded in the opening clause and every subsequent clause maps to a returned field, so there is little waste. The phrasing is somewhat idiosyncratic ('as its page shows it', 'what the cell cannot see about it'), which trades a little precision for compactness but does not bloat the text.

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?

For a one-parameter read tool with an output schema present, the description covers what the agent needs: what the call reports, what the parameter means, and what happens on a bad value. With no annotations, the definition still makes the read-only nature and the fallback behavior evident, so nothing essential is missing.

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?

Schema description coverage is 0% and the single parameter has no description in the schema, so the description must compensate — and it does: '`service` is its name' establishes a free-form name rather than an ID, and the unknown-name clause explains the failure mode and what the agent gets back. Format hints (case sensitivity, fully-qualified names) are absent, which keeps it below 5.

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?

The description names a specific resource (`service`) and enumerates exactly what the report covers: state in words, emitted signals (logs, metrics, traces, deploys), watchers, last-check time, incidents, and blind spots. An agent can tell this is a single-resource health/status read. It stops short of naming or contrasting with the obvious sibling `how_is_project`, so it is clear but not sibling-differentiated.

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: 'How one service is doing' signals a status check for one named service. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as `how_is_project` or `what_is_broken` for aggregate health. The unknown-name fallback is the only explicit behavioral rule offered.

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