Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Stop Entity Monitoring

stop_entity_monitoring
DestructiveIdempotent

Stop monitoring a registered entity so webhooks cease while the paid term continues; resume free until it ends. Retry after a 409 if an order is still processing.

Instructions

Stop monitoring an entity now. Webhooks stop immediately; the paid term keeps running (no refund) and the entity can be resumed free until it ends; stopped time is not added back. Safe to repeat. 409 order_processing while an order/renewal for it is still processing — retry in a few minutes.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "stop_entity_monitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (destructive=true, idempotent=true), the description discloses the non-obvious business consequences: webhooks cut off immediately, no refund, the paid term keeps running, free resumption until term end, and no time credit back. It also confirms repeat-safety and documents the 409 error with retry timing, which annotations alone could not 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?

Front-loaded with the action, then consequences, then idempotency, then the error case. Semicolons compress the billing rules without losing meaning; no sentence is filler.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers effects, billing, idempotency, and the failure mode. The remaining gap is operational: it never says how to obtain a valid entity_id or what resuming costs in terms of a separate call.

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?

The schema has one required parameter (entity_id) with 0% description coverage and no enum. The description refers to 'an entity' but adds no format, source, or acquisition hint (e.g., from list_monitored_entities), so it does little to compensate for the schema gap.

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 opening sentence gives a specific verb and resource ('Stop monitoring an entity now') with immediate effect. It also sketches the consequence envelope (webhooks stop, paid term continues), which separates it from the sibling mutation tools, though it never names start_entity_monitoring or resume_entity_monitoring directly.

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 states the situation for use ('Stop monitoring an entity now') and gives an explicit recovery path for the 409 order_processing condition ('retry in a few minutes'). What is missing is an explicit contrast: when to prefer resume_entity_monitoring over stopping, or that stopping is unnecessary if the intent is only temporary pausing.

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