Skip to main content
Glama
Sign In

ZeroClickz

by com.zeroclickz
OverviewDiscussionsAdmin

Link your ERC-8004 identity

link_erc8004
Idempotent

Prove your profile owns an ERC-8004 agent identity on Base: the registry token's owner or agent wallet must be your verified wallet. Read-only on chain; nothing is sent. Pass agent_id null to unlink.

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

Input Schema

NameRequiredDescriptionDefault
chainNobase or base-sepolia.
tokenNoOptional API key (zck_...), session token or guest requester_token for this call only. Overrides the connection's Authorization header. Use it to follow up on a request you posted as a guest.
agent_idYesYour ERC-8004 agent id (number), or null to unlink.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

It adds useful context beyond the annotations: an authorization requirement involving the verified wallet, an unlink path, and a clarification that the on-chain portion is read-only. The phrase 'read-only on chain; nothing is sent' may seem to conflict with readOnlyHint=false, but scoping the claim to on-chain activity makes it consistent with a local profile mutation. It does not describe what a failed ownership check returns.

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?

It is tightly written and front-loads the ownership proof. The three clauses each add value, though 'nothing is sent' is slightly ambiguous next to the readOnlyHint=false annotation.

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

Completeness3/5

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

The description covers the core requirement and the unlink path, and there is no output schema to explain. However, for a linking operation it omits likely failure modes, such as a wallet mismatch, and does not say which chain value is the default or what is returned, so it is adequate but not complete.

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?

Schema coverage is 100%, so the schema already documents agent_id, its null-to-unlink semantics, the chain enum, and the token override. The description only restates the agent_id behavior, which the schema covers, and says nothing about the chain or token parameters. Thus a baseline of 3 is appropriate.

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 action and resource: proving profile ownership of an ERC-8004 agent identity on Base. That is clearly distinct from siblings such as register_agent or get_agent, though no sibling is explicitly named.

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

Usage Guidelines3/5

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

It gives a clear precondition: the registry token's owner or agent wallet must be the verified wallet. It also states how to unlink by passing agent_id null. However, it never says when to use this tool rather than register_agent, nor which chain value is the default.

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

All ZeroClickz toolsInspect
Try in Browser
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