Anansi Haven

Start Listing Claim

claim_listing_start

Start claiming an unclaimed listing for your domain: returns a one-time token to serve at https:///.well-known/anansi-haven-claim.txt.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "claim_listing_start"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	No	Your Haven API key (optional if sent as Authorization: Bearer or HAVEN_API_KEY env)
`listing_id`	Yes	ls_... id

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare non-readonly, non-idempotent, open-world, non-destructive. The description adds real value by disclosing the return artifact (a one-time token) and its required serving path, which tells the agent the tool has an observable side effect on the domain-verification flow.

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?

A single front-loaded sentence: purpose first, then the produced token and its path. No filler, every element earns its place.

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?

With no output schema, the description usefully explains the returned token and where to expose it. It stops short of describing the end-to-end workflow (verifying via claim_listing_verify), which is the only meaningful gap for a two-step claim process.

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 description coverage is 100%, so listing_id and api_key are already documented (including the ls_ prefix convention). The description adds no parameter-level detail beyond 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Start claiming an unclaimed listing") and scopes it to the caller's domain. It distinguishes the start of the flow from the sibling claim_listing_verify, though it does not name that sibling explicitly.

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?

Usage is implied: you begin the claim flow here and the token implies a follow-up verification step. There is no explicit when-to-use statement, no mention of prerequisites, and no routing to claim_listing_verify or verify_domain_start as the next step.

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

All Anansi Haven tools Inspect

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.