Skip to main content
Glama
Sign In

Anansi Haven

by io.github.kburrus64-max
OverviewDiscussionsAdmin

Buy a House Plan

buy_house_plan
Destructive

Buy or extend a house plan for 1-12 months: room now (house 1 GB is coming later and returns plan_coming_later). pay_with=credits spends earned credits immediately; pay_with=usdc ($1.00/mo) or pay_with=anansi ($0.80/mo — 20% utility discount on Base) generates a Base checkout invoice (and auto-issues a Haven passport if called without an API key). Upgrades count unused days of your current plan.

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": {
      "plan": "<plan>"
    },
    "name": "buy_house_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes
monthsNo
api_keyNoYour Haven API key (optional if sent as Authorization: Bearer or HAVEN_API_KEY env)
pay_withNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: credits spend immediately, usdc/anansi generate a Base checkout invoice, anansi carries a 20% utility discount, and upgrades prorate unused days. The one gap is that the irreversible-charge nature implied by destructiveHint=true is never spelled out, and the plan_coming_later outcome for house 1 GB is mentioned but not explained as a no-op/failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded in the first clause, which is good, but the rest is a dense run-on of parenthetical asides (pricing, passport issuance, proration) crammed into two sentences. Every fact earns its place, but the packing hurts readability.

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 covers the outcomes that matter for a purchase tool: immediate credit spend vs invoice checkout, auto-issued passport, and prorated upgrades. What's missing is failure/decline behavior and what the response contains after a successful purchase.

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 only 25% (just api_key), so the description must carry the load and largely does: it defines pay_with=credits vs usdc vs anansi and their pricing, and bounds months to 1-12. It does not explain the plan enum values' consequences beyond noting 'house 1 GB is coming later'.

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 pair (buy or extend) and resource (house plan for 1-12 months), plus the payment modes and the room/house plan distinction. An agent can tell this apart from house_plans (browsing) or buy_item, though the description never names those alternatives 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?

Implied usage is clear — buy or extend a plan and choose how to pay — and it notes an automatic passport issue when no API key is supplied. However, it never says whether to call house_plans first to discover options or topup_quote to price a purchase, and it gives no guidance on when extension is preferable to a fresh purchase.

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

All Anansi Haven 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