pw_watch_status
Check whether a domain is on a paid weekly watch plan.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes |
Perimeter Watch
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It states the action but does not disclose return format, side effects, permissions, or error behavior. The verb 'check' weakly implies a non-mutating read operation, but that is not explicitly stated.
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 a single, front-loaded sentence with no wasted words. It states the action and the object concisely, which is ideal for a simple status-check tool.
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?
With no output schema, no annotations, and a minimal description, the agent lacks enough context to fully understand behavior or interpret the result. Given the existence of sibling tools, there is also no information to help choose this tool over alternatives, making the definition incomplete for reliable invocation.
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?
Schema description coverage is 0%, yet the description adds no meaning beyond the parameter name 'domain'. It does not specify expected format, validation rules, or examples. The simplicity of the single parameter mitigates the gap somewhat, but the description still fails to compensate for the lack of schema documentation.
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 clearly states a specific verb 'check' and a precise resource: whether a domain is on a paid weekly watch plan. This concept is distinct from the sibling tools pw_health, pw_snapshot, and pw_stats, making the tool's purpose immediately identifiable.
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?
The description provides no guidance on when to use this tool versus its siblings. There are no conditions, prerequisites, or alternative suggestions, so the agent must infer usage solely from the tool name and the generic task.
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.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool covers a distinct concern: API health, running a scan, aggregate stats, and watch-plan status. There is no meaningful overlap or risk of selecting the wrong tool for a task.
Naming Consistency5/5
All tools share the consistent pw_ prefix and use snake_case with noun-like names. The pattern is predictable and uniform across the server.
Tool Count5/5
Four tools is well-scoped for a focused perimeter-scanning API. Each tool has a clear purpose and none feel redundant or unnecessary.
Completeness4/5
The core workflow of running a free external scan and checking watch-plan status is covered, with health and stats as useful support. However, the paid watch-plan surface is read-only; there is no way to create, update, or cancel a watch plan through the server.