Skip to main content
Glama

Claim the Library address

claim_library
DestructiveIdempotent

Check (dryRun) or claim the public address of the workspace's Library, https://.unplain.page, where every lead magnet is published. A workspace has one Library and it is not created automatically. Ask the user which address they want; never choose one for them. Only the workspace owner can claim or change it, and changing an existing address needs confirmChange: true because every published link moves.

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

Input Schema

NameRequiredDescriptionDefault
dryRunNoOnly check whether the address is available; claim nothing.
subdomainYesThe address the USER chose: 3 to 32 lowercase letters, numbers or single hyphens. Never invent one.
confirmChangeNoRequired to CHANGE an address the Library already has: every published link moves (the old address redirects for 90 days). Confirm with the user first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses the real consequences: every published link moves, the old address redirects for 90 days, a workspace has only one Library, and claiming requires workspace-owner rights. These are exactly the facts an agent needs before triggering a destructive, link-breaking change.

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?

Three tightly packed sentences with the capability stated first, then the invariants, then the safety constraint. No filler, though the final clause about links moving is repeated from the schema and could be trimmed.

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 3-parameter mutation tool with no output schema, the description covers preconditions, consequences, and user interaction adequately. It does not state what a dryRun check returns (available/unavailable, suggested alternatives), which is the one remaining gap for an agent deciding its next step.

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% and the schema already documents dryRun, subdomain constraints, and the 90-day redirect behind confirmChange. The description reinforces the user-choice constraint on subdomain and the change-confirmation rule but adds little parameter meaning not already present in the schema, so the baseline 3 applies.

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 names a specific verb pair (check/claim) and a specific resource (the workspace Library address, with the literal URL shape https://<subdomain>.unplain.page). It also clarifies that a workspace has exactly one Library and it is not created automatically, so an agent can distinguish this from the lead-magnet creation siblings.

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?

Clear when-to-use rules: dryRun to check availability only, confirmChange: true required to change an existing address, owner-only authorization, and an explicit instruction to ask the user for the address rather than invent one. It does not route to a named alternative tool, which keeps it 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources