Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Resume Entity Monitoring

resume_entity_monitoring
Idempotent

Resume monitoring for a stopped entity while its paid term is active, at no cost; changes during the pause are not sent. Use renewal if the term has ended.

Instructions

Resume a stopped entity whose paid term is still running (free). Changes that happened while stopped are not sent. 422 not_resumable = term already ended -> renew_entity_monitoring instead; 422 acn_not_eligible / abn_not_active = the company was deregistered / ABN cancelled meanwhile.

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": "resume_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.4/5.0
Behavior4/5

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

Annotations declare non-read-only, idempotent, non-destructive, open-world, so the safety profile is partly covered. The description adds real behavioral context beyond them: the operation is free, and events that occurred while stopped are permanently not delivered, which is a consequential side effect an agent should surface. It does not cover permissions or auth, but the error semantics largely compensate.

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 core action and its precondition, then the key side effect, then a compact error-to-cause-to-alternative mapping. No sentence is padding, and the arrow shorthand is readable.

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?

An output schema exists so return values need not be explained, and the mutation's preconditions and failure modes are covered. It stops short of mentioning auth/permission requirements or the source of the entity_id, which would make it fully self-sufficient for a cross-account monitoring mutation.

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?

Single required parameter entity_id with 0% schema description coverage, and the description never explains it or says where an id comes from (e.g. list_monitored_entities). Since the parameter is self-evidently an entity identifier and only one exists, the gap is modest but real.

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?

Names a specific verb and resource (resume a stopped entity) and scopes it precisely to those 'whose paid term is still running'. It also distinguishes itself from renew_entity_monitoring for the term-ended case, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition (entity stopped, term still running) plus an explicit when-not with the alternative named (422 not_resumable -> use renew_entity_monitoring). The error-code-to-cause mapping (acn_not_eligible / abn_not_active) further tells the agent when resuming is impossible.

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