Skip to main content
Glama

Resolve a .theta name

name_resolve
Read-onlyIdempotent

Resolves a .theta name on TNS: owner, resolver, addr and the wave.bot, wave.site, wave.dapp, wave.avatar records (null if unset). Cached 60 s. Use bots_inspect for a bot's manifest. Read-only, free, no key. Bad name: error bad_args.

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

Input Schema

NameRequiredDescriptionDefault
nameYesA .theta name, lowercase, e.g. wave.theta or clerk.bots.theta

Output Schema

NameRequiredDescriptionDefault
addrNo
nameNo
blockNo
ownerNo
staleNo
sourceNo
recordsNo
resolverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"e.g. wave.theta"New value: +"A .theta name, lowercase, e.g. wave.theta or clerk.bots.theta"
    • addedInput schema / properties / name / pattern
      Added value: +"^[a-z0-9-.]+\\.theta$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "addr": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "owner": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "records": {
      +      "type": "object"
      +    },
      +    "resolver": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world; the description goes well beyond by disclosing caching (60 s), cost (free), and auth requirements (no key), plus the null-if-unset return behavior and the error code. That is exactly the kind of operational context annotations cannot carry.

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?

Two dense sentences, front-loaded with the resolve action and return shape, then the alternative, then operational facts. No filler, no repetition of the title, and the most decision-relevant information (returns + caching + free/no key) comes first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema, everything needed to call it correctly is present: valid input shape, error behavior, caching implications, cost/auth, and where to go for a different need. Nothing material is left to inference.

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% and already supplies the pattern and example, so the baseline would be 3. The description adds a failure contract the schema cannot express — "Bad name: error bad_args" — telling the agent what happens when the name is invalid, which is useful semantic context for the sole parameter.

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?

States a specific verb and resource ("Resolves a .theta name on TNS") and immediately enumerates what is returned: owner, resolver, addr, and the four wave.* records. It also names the sibling it is not (bots_inspect), so an agent can distinguish it without opening any schema.

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?

Explicitly routes the agent: "Use bots_inspect for a bot's manifest," giving one concrete alternative and the condition that selects it. It lacks broader when-not guidance (e.g., when to use theta_balance or agent_profile instead), so it stops short of a full routing rule set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources