Skip to main content
Glama

Check ENS permissions

get_permissions
Read-onlyIdempotent

Check what an account may do with an ENS name, e.g. 'Can 0xabc… change the records of alice.eth?'. Returns, for each action, true (allowed), false (not allowed) or null (unknown): set records, transfer, set the resolver, create or remove subnames, renew, and more. Also lists burned NameWrapper fuses and, for ENSv2 names, the account's roles. To see who owns or manages the name, use get_name_details.

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>",
      "account": "<account>"
    },
    "name": "get_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15)
accountYes

Output Schema

NameRequiredDescriptionDefault
canYes
nameYesENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15)
fusesYesBurned NameWrapper fuses limiting what anyone can do with the name
rolesNoThe account's ENSv2 roles on the name's registry
statusYes
accountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description focuses on what the annotations cannot say: the tri-state true/false/null result semantics and the presence of burned NameWrapper fuses and ENSv2 roles in the response. It does not discuss rate limits or pagination, but for a read-only lookup of this shape that is a minor omission.

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?

Purpose is front-loaded, followed by the example, the return contract, and the sibling pointer, in that order. Every sentence contributes distinct information and none restates the title or annotations.

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 two-parameter read tool with an output schema, the description covers purpose, the meaning of the null case, the scope of returned actions, and the alternative tool. Nothing needed to call it correctly or interpret its answer is missing.

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 only 50%: 'name' is documented in the schema but 'account' carries just a regex pattern. The example 'Can 0xabc… change the records of alice.eth?' supplies the missing semantics by showing that account is a 0x address and name is a human-written ENS name, so the description partly compensates for the coverage gap.

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 (check what an account may do with an ENS name) and grounds it with a concrete example question. It also explicitly distinguishes itself from get_name_details, so an agent can separate permission checking from ownership inspection without opening either schema.

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

Usage Guidelines5/5

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

The example question defines the exact use case, and the closing sentence routes the agent to get_name_details when the question is about ownership or management rather than capability. That is an explicit alternative with the condition that selects it.

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.