Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

Identify an address, hash, or name

singularityagent__resolve
Read-only

Work out what an arbitrary string is — an address, transaction hash, ENS/SNS name, or block height — and which chains it could belong to. Resolves names to addresses and does reverse ENS lookups. Call this first whenever the chain is not already known.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoChain id or alias, when you already know it.
inputYesAn address, transaction hash, ENS/SNS name, or block number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / properties
      Added value: +{
+  "chain": {
+    "description": "Chain id or alias, when you already know it.",
+    "type": "string"
+  },
+  "input": {
+    "description": "An address, transaction hash, ENS/SNS name, or block number.",
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "input"
+]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral detail beyond that: it resolves names to addresses, performs reverse ENS lookups, and enumerates the kinds of arbitrary strings it understands, including block heights and chain membership.

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

Conciseness5/5

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

Three short sentences cover purpose, capabilities, and usage guidance with no filler. The most important routing instruction is placed last but is still economical and easy to parse.

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 simple two-parameter, read-only resolver with no output schema, the description covers input semantics, resolution behavior, and the key use-before-chain-known scenario. It does not describe the exact return format or error behavior, but the annotation profile and schema make this a minor gap.

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%, with both `input` and `chain` documented. The description adds value on top by clarifying that `input` is an arbitrary string potentially of several types, and by tying the optional `chain` to the 'when already known' context, reinforcing when to provide it.

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?

The description uses a specific verb ('work out') and names the exact resource types the tool handles: address, transaction hash, ENS/SNS name, and block height. It also clarifies the tool identifies candidate chains, which distinguishes it from chain-specific sibling tools like singularityagent__transaction or singularityagent__read_contract.

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?

The explicit directive 'Call this first whenever the chain is not already known' gives a clear when-to-use rule. It implies that chain-specific tools should be used when the chain is known, but it does not name alternatives or state exclusions explicitly.

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

All Rokha toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources