Skip to main content
Glama
Sign In

spacesheep

by dev.spacesheep
OverviewDiscussionsAdmin

watch_space

Idempotent

Email the signed-in person when someone else writes to a space's records: a form, an RSVP, a booking, a poll, a guestbook. The first write is emailed at once, then at most one digest an hour while writes keep coming ("12 new responses"), each with a link to the page and a one-click stop. The email says how many and links the page; it never quotes what people wrote. Their own writes don't count. Needs a space they own or can edit. Watching the same space again returns the watch that exists. Returns the watch id.

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": {
      "space": "<space>"
    },
    "name": "watch_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat the watch is for, in a few words the email repeats, e.g. 'RSVPs for Sam's birthday'.
spaceYesThe space to watch, as a link, @handle/slug or uuid.
collectionNoOnly this records collection (e.g. 'rsvps'). Leave out to watch every collection the page writes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare the operation is not read-only and is idempotent, and the description adds substantial behavioral context beyond that: immediate first email, hourly digest cap while writes continue, email contents ('how many' plus a link, never quoting the content), and a one-click stop. This is exactly the extra context annotations cannot convey.

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?

The purpose is front-loaded in the first clause, and every following sentence delivers a distinct, load-bearing fact (cadence, content privacy, prerequisite, idempotency, return value). No sentence is filler despite the length.

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?

With no output schema, the description correctly closes the loop by stating what is returned ('Returns the watch id'). Combined with the ownership prerequisite, idempotency behavior, and notification semantics, an agent has everything needed to call and reason about this tool.

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 the schema already documents 'space', 'collection', and 'note' fully. The description reinforces collection scope ('every collection the page writes') but adds little syntax or format meaning 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.

Purpose5/5

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

The description states a specific verb and resource ('Email the signed-in person when someone else writes to a space's records') and enumerates concrete record types (form, RSVP, booking, poll, guestbook). It clearly separates this from siblings like stop_watch or list_watches, which an agent could otherwise confuse with it.

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

Usage Guidelines4/5

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

It gives a clear precondition for use ('Needs a space they own or can edit') and a scoping rule ('Their own writes don't count' and 'watching the same space again returns the watch that exists'). It does not name the counterpart tool (stop_watch) to explicitly route the agent, so 4 rather than 5.

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

All spacesheep 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