Skip to main content
Glama
stevysmith

stacktree-mcp

by stevysmith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

claim_site

Claim an anonymous page with its claim token to adopt it into your account, preserving URL, ID, and read history. This stops the 24-hour expiry and transfers update access to your key.

Instructions

Adopt a page that was published without an account into the account this key belongs to. Pass the claim_token from the anonymous publish response. Do this whenever you published anonymously and a key is now available: an unclaimed free page dies at 24 hours, and claiming gives it the longest life the plan allows, never a shorter one, with the same URL, id, token and read history. A claim IS a publish: on a free key it spends one of the three lifetime pages and can return 402 plan_lifetime_limit_exceeded or 429 plan_site_limit_exceeded, and the claim link stays valid until the page expires, so report the wall rather than retrying. A wallet-paid page is the exception: it spends no quota and keeps the permanence it paid for. Claiming SPENDS the claim_token — it stops being the page's keyless update credential and update_site takes over. Re-claiming a page this account owns answers already: true; 409 already_claimed, 403 invalid_claim_token and 410 are all final.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_or_slugYesThe site id from the anonymous publish response.
claim_tokenYesThe secret claim_token from that same response. Sensitive: anyone holding it can adopt the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure, and it does so thoroughly. It reveals quota consumption, 402/429 failure modes, finality of 409/403/410 errors, claim_token consumption, and the fact that a claim is effectively a publish.

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 definition is long but dense; nearly every clause carries operational information. It front-loads the core action and token requirement, then layers in side effects, exceptions, and terminal error semantics with no filler.

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?

The description thoroughly covers invocation context, side effects, error codes, and credential lifecycle. Without an output schema, it stops just short of explicitly describing the successful claim response shape, though the mention of re-claiming returning true offers some signal.

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 a baseline of 3 applies, but the description adds meaningful context beyond the schema. It establishes that both parameters come from the same anonymous publish response, emphasizes that claim_token is sensitive, and explains what claiming does to the token's role.

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 opens with a specific verb and resource: 'Adopt a page that was published without an account into the account this key belongs to.' It clearly differentiates claim_site from siblings like publish_html and update_site by tying it to anonymous publish responses and the claim_token.

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?

It explicitly states when to use this tool: 'Do this whenever you published anonymously and a key is now available.' It also covers exclusions and alternatives, noting that wallet-paid pages are an exception and that update_site takes over after claiming.

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

Deploy Server

Other Tools