OMENZ agent tools

freshness

Source Freshness / Result TTL: how long can your agent reuse a result before paying to fetch it again? The source's own Last-Modified, ETag and Cache-Control + a reuse window by data kind (price, quote, hours, weather, news, stock, crypto, business_facts, terms, docs, filing, profile, search) + how to revalidate cheaply (304). By OMENZ. (MCP calls run in AYNE, the free playzone; production: GET https://www.omenz.org/api/tollbooth/v1/freshness, $0.001 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": "freshness"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`kind`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.6/5.0

Behavior4/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 well: it discloses pricing ($0.001 via x402 in production, free in the AYNE playzone), the underlying signals inspected, and cheap revalidation via 304. It does not say whether the tool performs a live network fetch of the URL, nor any rate limits or failure behavior.

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?

Core meaning is front-loaded, but the definition is a single dense run-on with nested parentheses, a rhetorical opening question, a vendor byline, and a production endpoint/price block. Some of that earns its place; the byline and question framing do not.

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?

For a two-parameter tool with no output schema, the description should sketch the return values, and it partially does (a reuse window per data kind plus revalidation guidance). It leaves the practical output shape and whether a fetch occurs unstated, which are the remaining gaps an agent would want closed.

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 0%, so the description must compensate, and it largely does: the 'url' parameter is contextualized as the source whose Last-Modified/ETag/Cache-Control is read, and the 'kind' parameter receives an explicit value list (price, quote, hours, weather, news, stock, crypto, business_facts, terms, docs, filing, profile, search). It omits the default behavior when 'kind' is not supplied.

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 the resource and the quantity it computes: source freshness / result TTL, derived from Last-Modified, ETag and Cache-Control plus a per-kind reuse window. An agent can tell this is a caching/freshness lookup rather than a data fetch, though the framing is a rhetorical question rather than a clean verb+object statement.

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 implied by the phrase 'how long can your agent reuse a result before paying to fetch it again', which suggests calling it before re-fetching. There is no explicit when-to-use, when-not-to-use, or comparison against adjacent siblings like 'changed' or 'alive'.

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?