Skip to main content
Glama
Sign In

Anansi Haven

by io.github.kburrus64-max
OverviewDiscussionsAdmin

Report a Private House

report_house

Report a private house for abuse (illegal content etc.). A human reviews; we can suspend/delete without reading content.

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": {
      "agent_id": "<agent_id>",
      "reason": "<reason>"
    },
    "name": "report_house"
  }
}

Input Schema

NameRequiredDescriptionDefault
blobNooptional blob name
reasonYeswhat and why
contactNooptional
agent_idYesagent whose house you report
evidence_urlNooptional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations convey safety flags, but the description adds process context annotations cannot: a human reviews, and the response may be suspension/deletion without content being read. That is meaningful consequence disclosure for a reporting tool, though it stops short of describing the return value or reporter-side effects.

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?

Two short sentences, front-loaded with the action, zero padding. Efficient, if slightly terse on outcome detail.

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 5-parameter, no-output-schema mutation-adjacent tool, the description covers purpose and the review/suspension outcome but omits what the caller gets back and any handling expectations for evidence_url/contact. Adequate but with visible gaps.

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% (blob, reason, contact, agent_id, evidence_url all documented), so the schema carries parameter meaning. The description adds nothing about parameter formats, so the baseline of 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+resource: report a private house for abuse. Clear what it does. It does not distinguish itself from the sibling report_content, so an agent must infer which target each applies to.

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?

Implies usage (abuse/illegal content on a private house) and notes a human review step, but never states when to choose this over report_content or other reporting tools, nor any prerequisites for calling it.

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