Skip to main content
Glama
Sign In
Delx MCP Server

Delx MCP Server

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Api Health Report

util_api_health_report
Read-onlyIdempotent

Probe any URL to measure status, latency, redirects, content type, and reachability in a single request.

Instructions

Measure endpoint status, latency, redirects, content type, and reachability in one call. Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL to probe
timeoutNoTimeout in seconds (1-15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive nature. Description adds that it bundles multiple metrics in one call and mentions potential x402 utility pricing, which is useful behavioral context beyond annotations.

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 efficient sentences. First sentence states core function; second sentence adds relevant context. No unnecessary words.

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?

Lacks description of output format, which is important for an agent to interpret results. With no output schema, the description should at least hint at return structure. Otherwise, coverage is adequate for a simple read-only tool with annotations.

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 coverage is 100%, so baseline is 3. Description adds semantics for the url parameter by listing the specific metrics measured (status, latency, etc.), going beyond the schema's 'URL to probe'. Timeout parameter is not described in description but schema covers it.

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?

Clearly states it measures endpoint status, latency, redirects, content type, and reachability in one call. However, it does not differentiate from the sibling tool util_url_health, which likely has a similar purpose.

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?

No guidance on when to use this tool versus alternatives like util_url_health or util_domain_trust_report. The note about pricing is tangential and does not help with usage decisions.

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