Skip to main content

intel

by io.chainhelix

Overview Discussions Admin

buyer_clearance

Read-only

The standing clearance on file for a wallet: whether a cleared buyer record exists, its paid period, the current signed sanctions statement, how many times it has been renewed and when it renews next. Send an EVM address. A seller reads this before taking a job instead of paying for a screen

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": {
      "address": "<address>"
    },
    "name": "buyer_clearance"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	EVM address, 0x and 40 hex characters. Example: 0x000000000000000000000000000000000000dead

Output Schema

Name	Required	Description	Default
`how`	No
`error`	No
`active`	No
`onFile`	Yes
`result`	No
`wallet`	No
`current`	No
`network`	No
`renewals`	No
`enrolledAt`	No
`validUntil`	No
`howToVerify`	No
`currentFresh`	No
`nextRenewalAt`	No
`renewEveryHours`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / address / description

Added value: +"EVM address, 0x and 40 hex characters. Example: 0x000000000000000000000000000000000000dead"

Changed1 schema field changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"

Changed2 schema fields changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"New value: +"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"

changedInput schema / x-lexicon / version

Previous value: -"0.1.0"New value: +"0.2.0"

Changed1 schema field changedOct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed1 schema field changedSep 21, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"

Changed3 schema fields changedSep 19, 2026

addedInput schema / x-aliases

Added value: +{
+  "address": [
+    "Address"
+  ]
+}

addedInput schema / x-lexicon

Added value: +{
+  "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+  "name": "ChainHelix Agentic Lexicon",
+  "resolve": "lexicon_resolve",
+  "spec": "lexicon_spec",
+  "version": "0.1.0"
+}

addedInput schema / x-vocab

Added value: +{
+  "address": "onchain.addressApi"
+}

AddedSep 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description carries a lower burden. It adds the useful 'standing record on file' framing, but the returned fields it lists are largely restated by the output schema, and it says nothing about behavior for wallets with no record on file.

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 return contents come first and the usage hint follows; nothing is wasted. The trailing 'Send an EVM address' fragment is abrupt and slightly interrupts the sentence flow, keeping it at a 4.

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?

With an output schema present, the description need not spell out return values, and annotations cover the safety profile. Purpose, input, and usage context are all present; only the no-record-on-file behavior is left implicit.

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?

There is one parameter at 100% schema description coverage, including format and an example address, so the schema does the work. 'Send an EVM address' in the description adds nothing beyond it, making the baseline 3 correct.

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 (the standing clearance on file for a wallet) and enumerates its contents: cleared buyer record, paid period, signed sanctions statement, renewal count and next renewal date. It is not a plain verb+resource sentence, so it stops short of a 5, but an agent can tell exactly what it retrieves.

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?

'Send an EVM address' gives the call shape, and 'A seller reads this before taking a job instead of paying for a screen' supplies a concrete trigger and names the alternative it replaces (paying for a screen, i.e. the screening siblings like screened_payer). It stops short of naming when-not conditions or a sibling by tool name.

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

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?