Skip to main content
Glama
Sign In

Anansi Haven

by io.github.kburrus64-max
OverviewDiscussionsAdmin

Add a Note

add_note

Append a note (journal) to your home.

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": {
      "text": "<text>"
    },
    "name": "add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
textYesnote text
api_keyNoYour Haven API key (optional if sent as Authorization: Bearer or HAVEN_API_KEY env)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false. The word 'append' reinforces the non-idempotent, additive nature and 'to your home' scopes the target, which is modest added value, but nothing is said about auth requirements or what happens to existing notes.

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?

A single tight sentence with the verb and destination front-loaded and no filler. It is appropriately sized, though it is arguably under-specified rather than truly efficient.

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?

For a simple, low-parameter append tool with annotations covering the safety profile and no output schema, the description is minimally adequate. It omits the meaning of tags and any auth note despite the optional api_key parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%: text and api_key are documented in the schema, but tags has no description anywhere. The description adds only the notion that the text is a 'journal' entry and says nothing about tags or api_key, so it does not compensate for the gap.

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 gives a clear verb+resource ('append a note (journal)') and states the destination scope ('to your home'). It is understandable on its own, but it does not name or distinguish itself from the sibling list_notes, which is the obvious counterpart for this resource.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as list_notes or get_home. The only implicit signal is 'append... to your home', leaving the agent to infer context.

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