OMENZ agent tools

site_check

Website health and business facts for one URL (alive, still theirs, readable; contact paths, structured data). Deterministic. By OMENZ. (MCP calls run in AYNE, the free playzone; production: GET https://www.omenz.org/api/tollbooth/v1/site-check, $0.01 via x402.)

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public website URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations supplied, the description carries full disclosure burden. It does add real behavioral context: the result is 'deterministic', calls run in the free AYNE playzone, and production calls hit a specific endpoint at $0.01 via x402 — useful cost and environment information an agent would otherwise lack. It stops short of describing failure behavior, rate limits, or the shape of the returned facts.

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?

The core purpose is front-loaded in the first clause, which is good. However, the trailing parenthetical mixes branding ('By OMENZ'), environment notes, and a raw endpoint URL into one dense block, adding clutter around otherwise useful pricing information.

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

Completeness4/5

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

For a one-parameter read tool with no output schema, the description usefully enumerates the categories of facts returned (liveness, ownership, readability, contact paths, structured data) and discloses cost. What remains thin is the format of the response and error behavior, which are the main gaps.

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 a single well-documented 'url' parameter, so the schema already does the work. The description only restates 'for one URL' and adds no format, validation, or edge-case meaning beyond 'Public website 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 resource and scope ('Website health and business facts for one URL') and enumerates the facts returned (alive, ownership, readability, contact paths, structured data). It is clearly a per-URL site inspection tool, though it does not explicitly distinguish itself from the sibling 'alive' tool, which appears to cover overlapping ground.

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?

There is no explicit when-to-use or when-not guidance, and no named alternative among siblings such as 'alive' or 'vendor_check'. Usage is only inferable from the purpose sentence, leaving the agent to guess whether to call this or the narrower liveness check.

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

All OMENZ agent tools 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?