intel

hire_quote

Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Ask a hireable agent on BNB Smart Chain for a live signed ERC-8183 quote through ChainHelix: send your task description and terms, receive the signed offer envelope and the steps to fund the job. Only agents the live map lists as hireable

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`terms`	No
`task_description`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`error`	No
`terms`	No
`accepted`	No
`envelope`	No
`latencyMs`	No

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose authentication, payment cost, payment routes, accepted tokens, and output behavior: a signed offer envelope and funding steps. It also restricts the operation to live-map-listed hireable agents. The quote-only workflow avoids claiming side effects beyond generating a quote.

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?

The description is moderately long but each sentence carries needed information: prerequisite auth/payment, the actual request workflow, the expected output, and the hireable-agent restriction. The only redundancy is the repeated ChainHelix reference, and the payment rail enumeration is dense but relevant.

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?

The description covers the main workflow, payment prerequisites, expected output, and the hireable-agent limitation, while an output schema exists to carry return-value details. It is incomplete around the required 'id' field and the acceptable structure of 'terms', making the full request construction ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description must compensate. It partially does by mapping 'task_description' and 'terms' to the instruction to send a task description and terms, but it never explains the required 'id' parameter or the shape/semantics of the nested 'terms' object. An agent must guess what 'id' refers to before invoking the tool.

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 states a concrete action: ask a hireable agent on BNB Smart Chain for a live signed ERC-8183 quote, and explains what the caller sends and receives. It does not explicitly name a sibling tool to distinguish itself from, but the quote workflow is unmistakably different from the search, buy, claim, and report tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear context and gate: the tool is for getting a quote from an agent listed as hireable on the live map, and only with a ChainHelix API key or one of the listed payment paths. It does not explicitly list alternatives or when-not-to-use cases, so it stops just short of a full 5.

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

All intel tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but some overlap exists among report tools (situation_report, deep_report, market_state) and spec tools (attest_spec, proof_spec). These could confuse an agent selecting the most appropriate endpoint.

Naming Consistency4/5

Tool names use consistent snake_case and are descriptive, but follow mixed patterns: verb_noun for actions (buy_key, list_attestations) and bare nouns or noun phrases for data endpoints (prices, congestion, wall_map). This is readable but not fully uniform.

Tool Count3/5

With 26 tools, the set is heavy and covers multiple domains (attestation, market data, key management, webhooks). It sits just above the borderline for comfort, but the breadth is justifiable given the server's multi-purpose nature.

Completeness5/5

The tool surface provides full lifecycle coverage for attestation (create, read, verify), key management (buy, claim, status), and webhooks (register, status, unregister), plus a wide range of market data endpoints. There are no obvious gaps or dead ends.

Resources

Need Help?