Skip to main content
Glama

watch_area

Register a webhook that fires when a new matching venue opens in an area. criteria = {state, city, signal_type, min_opening_score}. Paid accounts only.

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

Input Schema

NameRequiredDescriptionDefault
urlYesHTTPS endpoint to POST matching venues to.
criteriaYes{state, city, signal_type, min_opening_score}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose the key behavior: it registers a webhook that fires when matching venues open, and it is restricted to paid accounts. It does not cover webhook lifecycle details such as duplicate registration, delivery retries, payload format, or how to remove or inspect the webhook.

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 description is two short sentences and front-loads the core action and event trigger. The criteria list and paid-account constraint are useful and compact, with no wasted wording.

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?

The tool is simple with two required parameters and no output schema, and the description covers the essential trigger and account restriction. However, nested criteria fields are only listed by name, and the description does not explain the webhook registration result or lifecycle, leaving some gaps for an agent.

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 parameter meanings are already documented. The description repeats the criteria fields but does not add semantic detail such as allowed signal_type values or the meaning/range of min_opening_score, so it stays at the baseline.

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: register a webhook that fires on a new matching venue opening in an area. It is clear enough for selection, but it does not explicitly distinguish this from related sibling tools such as new_openings or venue_signals.

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?

It gives an important eligibility constraint (paid accounts only), which helps determine whether the tool can be used. However, it does not say when to choose this webhook-registration tool versus checking openings or signals directly, so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources