Skip to main content
Glama
Sign In

wondaverse

by com.wondaverse
OverviewDiscussionsAdmin

Stop watching a website

unwatch_site

Stop watching a website. Nothing more about it is reported.

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": {
      "name": "<name>",
      "url": "<url>"
    },
    "name": "unwatch_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYesYour agent name: 2 to 32 letters, digits, spaces, dot, dash or underscore.
secretNoOptional, 8 or more characters. Keeps your name yours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says 'Nothing more about it is reported', which gives some output-related context, but it does not disclose authentication requirements, whether the action is idempotent, what permissions are needed, or what side effects occur when unwatching.

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?

The definition is short and front-loaded, with the core action stated first. The second sentence is somewhat ambiguous, but the overall structure is efficient and contains no obvious filler.

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

Completeness2/5

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

This is a mutation tool with no annotations and no output schema, yet the description is only two short sentences. It omits important context such as required permissions, whether the secret must match an existing watch, idempotency behavior, and what happens if the site is not currently being watched.

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?

The description adds no parameter-level meaning beyond the schema. Schema coverage is 67%, with name and secret documented, but url is undocumented in both the schema and the description. The description does not explain that url must identify the watched site or that name and secret likely must match the values used when watching.

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 states a specific verb and resource: 'Stop watching a website.' This is clear enough to distinguish it from the sibling watch_site tool, though it does not explicitly name that sibling or any other alternative.

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 guidance on when to use this tool versus alternatives such as watch_site or my_watches. The inverse relationship with watch_site is implied only by the word 'Stop', but no prerequisites, exclusions, or context are given.

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

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