agent-health

register_agent_health

Register a real worker once. Heartbeat mode needs no endpoint and reports contact only. Probe mode requires your own deployed readiness URL. Store the returned owner key securely; it is shown once. name, contact, note and version are public. Never invent monitoring activity.

Input Schema

TableJSON Schema

Name	Required	Default
`mode`	No	probe
`name`	Yes
`contact`	No
`agent_type`	No
`webhook_url`	No
`endpoint_url`	No
`checks_config`	No
`heartbeat_enabled`	No
`check_interval_sec`	No
`heartbeat_interval_sec`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 28, 2026

addedInput schema / properties / agent_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Agent Type"
+}

addedInput schema / properties / contact

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Contact"
+}

addedInput schema / properties / endpoint_url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / endpoint_url / default
```
Added value: +null
```
removedInput schema / properties / endpoint_url / type
```
Removed value: -"string"
```

addedInput schema / properties / heartbeat_interval_sec

Added value: +{
+  "default": 300,
+  "title": "Heartbeat Interval Sec",
+  "type": "integer"
+}

addedInput schema / properties / mode

Added value: +{
+  "default": "probe",
+  "title": "Mode",
+  "type": "string"
+}

addedInput schema / properties / webhook_url

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Webhook Url"
+}

changedInput schema / required

Previous value: -[
-  "name",
-  "endpoint_url"
-]New value: +[
+  "name"
+]

Changed1 schema field changedSep 12, 2026

addedInput schema / properties / checks_config

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Checks Config"
+}

First observedSep 9, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the agent knows this is a non-destructive write to an open system. The description adds useful context: owner key shown once, fields public, endpoint requirement per mode, and a warning against faking activity. It does not cover rate limits, idempotency, or what happens on re-registration.

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 description is four short sentences, front-loaded with the main action and mode distinction, and includes a security warning. It is efficient, though it omits some key parameters.

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

Completeness3/5

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

With an output schema present, return values need not be explained. However, for a 10-parameter mutation tool with no schema descriptions, the description covers only a fraction of the parameters and omits other important behavioral details like re-registration behavior or error handling. It is adequate but incomplete.

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 0%, so the description must compensate. It names and explains only a few parameters (name, contact, note, version) and the mode distinction, leaving most of the 10 parameters (endpoint_url, webhook_url, checks_config, intervals, etc.) undocumented in both schema and description. Baseline 3 because the description adds some meaning but does not fully cover the parameter set.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Register a real worker once' and distinguishes heartbeat vs probe modes, which clarifies what mode does. However, it doesn't clearly explain what an 'agent health' registration is or differentiate from siblings like update_agent_health or agent_health_heartbeat. The purpose is implied but not crisply stated.

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?

The description explains mode differences (heartbeat needs no endpoint, probe requires a URL), offering some implicit guidance. But there is no explicit when-to-use-this-vs-alternatives guidance, no mention of prerequisites, and no routing to sibling tools like update_agent_health or send_heartbeat.

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

All agent-health tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?