Taifoon coordination layer

taifoon_grid_hire

Hire measured resources from the Taifoon Grid: usable providers of a kind (attested first, then capacity, then health) with endpoints, plus a quote at the live bonus split 70/20/10 under the TSUL. Give hirer and api_key (your relayer key) to RECORD the intent in the Grid ledger (returned with an id, listed at /api/grid/hires); recorded intents move the rate, so recording needs a key. Settlement is not deployed — a quote reserves nothing.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes
`note`	No	optional, ≤200 chars, stored with the intent
`hirer`	No	your 0x address or agent id — when given, the intent is RECORDED in the Grid ledger (a record, not a settlement) and returned with an id
`hours`	No	for how long (default 1)
`units`	No	how many resources (default 1)
`api_key`	No	your relayer key (tfr_…) — REQUIRED to record an intent with `hirer` (recorded intents move the rate); without it you get the quote only

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / api_key

Added value: +{
+  "description": "your relayer key (tfr_…) — REQUIRED to record an intent with `hirer` (recorded intents move the rate); without it you get the quote only",
+  "type": "string"
+}

First observedSep 27, 2026

TDQS

A3.7/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 load and does well: it discloses provider ordering (attested, then capacity, then health), the 70/20/10 bonus split, that recording requires a key and mutates the rate, and that settlement is not deployed so a quote reserves nothing. Side effects and limitations are surfaced rather than hidden.

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-loads the core purpose in the first sentence, then handles recording and settlement caveats. Information-dense but every clause carries substance; minor jargon (TSUL) is unexplained.

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?

No output schema or annotations exist, so the description must cover behavior and it does: it explains the return payload (providers with endpoints, quote, id), the ledger side effect, and the non-settlement caveat. Only the alternative-tool selection is missing.

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 83%, so the schema already documents parameters. The description reinforces the hirer/api_key interaction (record vs quote-only), which is useful, but largely restates what the schema descriptions provide.

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?

States a specific verb (hire) and resource (measured resources / providers of a kind) with what it returns: endpoints plus a quote. It is clearly distinguishable from adjacent hire_* tools in intent, though it never explicitly names a sibling to contrast against.

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?

Gives the key conditional: supplying hirer + api_key records the intent, omitting the key yields quote-only. However it offers no guidance on when to choose this over alternatives like taifoon_pool_quote or taifoon_hire_suggest, leaving the routing to inference.

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

All Taifoon coordination layer 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?