Skip to main content
Glama

manage_fuses

Read burned fuses on an ENS name, burn owner fuses to restrict name actions, or burn parent fuses on subnames. Irreversible; fuses expire with the name.

Instructions

Manage fuses on a wrapped ENS name. Fuses are permission bits that can be permanently burned to restrict what can be done with a name.

Three modes:

  1. read — Check which fuses are currently burned on a name

  2. burn_owner_fuses — Burn fuses on a name you own (CANNOT_UNWRAP must be burned first)

  3. burn_child_fuses — As a parent, burn fuses on a subname (e.g. burn PARENT_CANNOT_CONTROL on sub.parent.eth)

Owner-controlled fuses:

  • CANNOT_UNWRAP — prevents unwrapping (MUST be burned first before any other fuse)

  • CANNOT_BURN_FUSES — prevents burning additional fuses

  • CANNOT_TRANSFER — prevents transfers

  • CANNOT_SET_RESOLVER — prevents resolver changes

  • CANNOT_SET_TTL — prevents TTL changes

  • CANNOT_CREATE_SUBDOMAIN — prevents creating new subnames

  • CANNOT_APPROVE — prevents approving operators

Parent-controlled fuses (for subnames):

  • PARENT_CANNOT_CONTROL — parent permanently gives up control over the subname

  • CAN_EXTEND_EXPIRY — allows the subname owner to extend their own expiry

WARNING: All fuse burning is IRREVERSIBLE. Fuses expire when the name expires.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesENS name to manage fuses on (e.g. "coffee.eth" for owner fuses, or "sub.coffee.eth" for child fuses)
fusesNoFuses to burn. Required for burn actions, optional for read. Owner fuses: CANNOT_UNWRAP, CANNOT_BURN_FUSES, CANNOT_TRANSFER, CANNOT_SET_RESOLVER, CANNOT_SET_TTL, CANNOT_CREATE_SUBDOMAIN, CANNOT_APPROVE. Parent-controlled fuses (for subnames): PARENT_CANNOT_CONTROL, CAN_EXTEND_EXPIRY.
actionNoAction: "burn_owner_fuses" burns fuses on a name you own, "burn_child_fuses" burns fuses on a subname you are parent of, "read" reads current fusesread
expiryNoFor burn_child_fuses only: Unix timestamp for subname expiry (cannot exceed parent expiry)
Behavior5/5

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

With no annotations provided, the description fully carries the burden and does so thoroughly. It warns that all fuse burning is irreversible, states that fuses expire with the name, and explains the consequences of each fuse type, offering complete transparency about side effects.

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?

The description is well-structured with clear mode headings and bullet lists. Each line serves a purpose, including the prominent irreversible warning. Despite its length, it earns its space by clearly organizing complex fuse rules.

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?

The description covers all modes, parameter usage, preconditions, and irreversible consequences, leaving minimal ambiguity for an agent. The lack of an output schema is mitigated by describing read mode as 'check which fuses are currently burned'. This is highly complete for a complex tool.

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%, so baseline is 3, but the description enriches parameter meaning by explaining the semantics of each fuse name, the role of expiry in child burns, and the difference between owner and parent fuses. This exceeds the schema's basic descriptions but could be even more detailed on edge cases.

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 clearly states the tool manages fuses on an ENS name, with three explicit modes: read, burn_owner_fuses, and burn_child_fuses. This distinguishes it from sibling tools like unwrap_name or wrap_name by focusing on fuse management.

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 provides clear when-to-use guidance for each mode, e.g., 'Burn fuses on a name you own' and 'As a parent, burn fuses on a subname', plus the prerequisite that CANNOT_UNWRAP must be burned first. However, it doesn't explicitly mention alternative tools or exclusions, so it falls just short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eggybug42069/namewhisper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server