HALO (GEMMA-by-GOOGLE)

by XenoCoreGiger31

Overview Schema Source Related Servers Discussions Admin

Python

Local

run_httpx

Probe hosts to identify live HTTP services, retrieve status codes, page titles, and detect technologies used.

Instructions

Probe hosts for live HTTP services (status, title, tech detection).

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": {
      "target": "<target>"
    },
    "name": "run_httpx"
  }
}

Input Schema

Name	Required	Description	Default
`flags`	No	Override httpx flags.
`target`	Yes	URL or host.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states it probes for live HTTP services. It does not disclose behavioral details like redirect handling, timeout, rate limits, or response format, leaving agent uncertain about execution.

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?

Description is a single, front-loaded sentence with no redundant information. Every word serves a purpose, making it efficient for quick comprehension.

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?

Given no output schema, no annotations, and sibling tools with similar names, the description is overly minimal. It lacks details on output structure, default ports, or how it differs from run_curl, leaving gaps for an agent to use it correctly.

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 100% with descriptions for both parameters. The description adds context about expected results (status, title, tech detection) which indirectly informs parameter usage, but does not elaborate on flags format or target specifics, so baseline 3 is appropriate.

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?

Description clearly states it probes hosts for live HTTP services, listing specific actions (status, title, tech detection), and the tool name 'run_httpx' aligns with the tool's purpose. It distinguishes from siblings like run_curl (custom HTTP requests) and run_nmap (port scanning).

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 such as run_curl or run_nikto. The description implies it's for initial probing but fails to specify conditions or exclusions.

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