Skip to main content
Glama

AIDNode | AI Agent Support Network

monitor

AIDNode Monitor v2: live independent HTTP HEAD/GET health and optional content digest check of approved public HTTPS hosts. On-demand only.

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": {
      "operation_id": "<operation_id>",
      "url": "<url>"
    },
    "name": "monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
methodNo
operation_idYesUnique call id 8-100 characters; counted once by beta ledger
expected_sha256No
expected_statusNo
max_duration_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / max_duration_ms
      Added value: +{
      +  "maximum": 30000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden and does add useful facts: the operation is a live, independent health probe limited to approved public HTTPS hosts, and the digest check is optional. However, it omits permissions/allowlist failure behavior, rate limits, timeout semantics, whether it is non-mutating, and what a result looks like.

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

Conciseness3/5

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

It is short and the operative content ('HTTP HEAD/GET health … of approved public HTTPS hosts') is front-loaded. But the 'AIDNode Monitor v2' branding and the dangling 'On-demand only.' fragment consume space without adding much, and the single long sentence is dense rather than crisp.

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

Completeness2/5

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

A six-parameter tool with no annotations and no output schema needs a description that explains result shape and the meaning of the remaining parameters. The definition covers the concept but not the contract, leaving an agent unsure how to interpret a response or what expected_status/max_duration_ms do.

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

Parameters2/5

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

Schema coverage is only 17% (just operation_id), so the description must compensate for six parameters. It only implicitly covers two of them ('HEAD/GET' maps to method, 'content digest check' maps to expected_sha256) and says nothing about expected_status, max_duration_ms, or the approval constraint on url.

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 verb and resource: live HTTP HEAD/GET health checks against approved public HTTPS hosts, with an optional content digest check. That is concrete enough to distinguish it from siblings like 'repair' or 'submit_beta_feedback', though it never explicitly contrasts with the closest-sounding sibling, 'verify'.

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?

'On-demand only' rules out scheduled/polling use and implies the tool is called per-request, which is real usage guidance. But there is no statement of when to prefer this over 'verify' or 'witness', and no mention of what happens when a host is not pre-approved.

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.