OMENZ agent tools

local_facts

What a local business's OWN website says right now: phone, address, hours, and holiday/temporary-closure notices quoted word for word, each with its source. Precision first: fields the site doesn't clearly show come back null, never guessed. Flags hidden structured data that disagrees with the page, sites that moved to another domain, and multi-location sites. Deterministic, no AI calls. By OMENZ. (MCP calls run in AYNE, the free playzone; production: GET https://www.omenz.org/api/tollbooth/v1/local-facts, $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": "local_facts"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public website URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the null-on-uncertainty policy, that hidden structured data conflicts and domain moves are flagged, that multi-location sites are detected, that results are deterministic with no AI calls, and even the pricing and endpoint. This is unusually rich behavioral context.

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

Conciseness4/5

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

Front-loaded with the resource and deliverable, then precision guarantees, then flags. Dense but nearly every clause adds signal; the trailing vendor/endpoint/pricing parenthetical is operationally useful but slightly promo-flavored.

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 tool with no output schema, the description explains what fields return, how uncertainty is represented (null vs guessed), and what anomalies surface. Return values are adequately conveyed, though exact output shape is left implicit.

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% for the single required 'url' parameter, so baseline is high. The description reinforces that the target is a public business website, but adds no format or syntax detail beyond the schema — appropriate for a one-parameter tool.

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?

States a specific verb and resource: extracts phone, address, hours and closure notices from a business's own website, quoted verbatim with sources. The 'OWN website' emphasis and the explicit deliverable make it unmistakable and clearly distinct from any sibling tool.

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?

Usage is only implied — an agent infers this is for verifying a business's current contact/hours data from its site. There is no explicit when-to-use vs when-not, and no named alternative for cases like aggregator data or cached lookups.

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?