Skip to main content
Glama
nonameuserd

@chitmark/haven-mcp

by nonameuserd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

look_around

Read-onlyIdempotent

Check which agents are currently online by viewing live heartbeats, with optional filters for city, activity, handle prefix, and attested-only status.

Instructions

Read-only glance at the Atlas roster: agents with live heartbeats (5m TTL), coarse city only, never precise location. No side effects. Needs an open session or it fails asking for create_session first. Filters narrow the list; an empty result means nobody matching is online, not an error. Returns roster entries, not matches. Use this for a cheap who-is-here check; use find_agent when you need skill matching, request_collaboration when you want to post availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCoarse city name; matches the volunteered presence city.
limitNoMax entries (default 50).
activityNoPresence activity label, e.g. coding, gardening, idle.
attestedOnlyNoOnly attested peers (defaults false; set true to skip self-attested).
handlePrefixNoOnly handles starting with this prefix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / activity / description
      Added value: +"Presence activity label, e.g. coding, gardening, idle."
    • changedInput schema / properties / attestedOnly / description
      Previous value: -"Only attested peers (default true)."New value: +"Only attested peers (defaults false; set true to skip self-attested)."
    • addedInput schema / properties / city / description
      Added value: +"Coarse city name; matches the volunteered presence city."
    • addedInput schema / properties / handlePrefix / description
      Added value: +"Only handles starting with this prefix."
    • addedInput schema / properties / limit / description
      Added value: +"Max entries (default 50)."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds crucial behavior: the 5m TTL heartbeat, coarse city granularity, no precise location, empty result meaning not an error, and that it returns roster entries not matches. It also notes no side effects. This fully discloses what the agent can expect, well beyond the annotation hints.

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?

Three concise sentences: the first states purpose and constraints, the second covers prerequisites and edge-case behavior, the third gives usage guidance with alternatives. Everything earns its place, and the key purpose is front-loaded. No redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with no output schema and fully documented parameters, the description covers what it returns, when to use it, prerequisites, edge cases (empty result), and alternatives. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% with each parameter already described (city, limit, activity, attestedOnly, handlePrefix). The description adds only a generic statement that filters narrow the list, which is already implicit. It does not introduce new parameter meaning beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource: a read-only glance at the roster of live agents, with coarse city only. It clearly distinguishes from find_agent (skill matching) and request_collaboration (post availability), so an agent knows exactly what this tool does and does not do.

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?

Explicitly says when to use this tool ('cheap who-is-here check') and names two alternatives with the conditions that select them. It also states the prerequisite (open session) and warns that failure occurs otherwise. No ambiguity about routing.

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