Skip to main content
Glama
Sign In
Keel

Keel

by seayniclabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

http_check

Perform HTTP requests to measure timing breakdown including DNS, connect, TLS, TTFB, total, along with status code, response size, and headers.

Instructions

Perform an HTTP request and return timing breakdown.

Returns status code, timing (DNS, connect, TLS, TTFB, total), response size, and headers.

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": "http_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention important traits like whether the tool follows redirects, handles timeouts, or requires specific HTTP methods. The description only lists return values.

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?

The description is two sentences, front-loads the action ('Perform an HTTP request'), and lists return values efficiently without extraneous 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?

Given the tool has one parameter, no output schema, and no annotations, the description covers the basic purpose and return values. However, it lacks key operational details like timeout behavior, redirect handling, or authentication, making it minimally adequate.

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?

The single parameter 'url' is required but lacks any description in the schema. The description does not add additional meaning beyond 'perform an HTTP request,' leaving the agent without details on expected URL format or constraints.

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 clearly states the tool performs an HTTP request and returns a timing breakdown, status code, response size, and headers, which distinguishes it from sibling tools like ping, traceroute, and DNS lookups.

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?

The description does not explicitly state when to use this tool versus alternatives, nor does it provide any context on prerequisites or exclusions. There is no guidance on when not to use it.

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