Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Monitored Entity

get_monitored_entity
Read-only

Retrieve a monitored entity's details by ID to verify ownership and current registry status. Use it after listing entities to confirm an ID is valid in your account and environment.

Instructions

One monitored entity (see list_monitored_entities for the object). 404 not_found if it is not yours in this environment (ids are per account and per environment; a merged ABN entity's old id also returns 404 — re-read the list).

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": "get_monitored_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds genuinely non-obvious behavior: a 404 not_found is returned when the entity is not owned in this environment, and ids are scoped per account and per environment. The merged-ABN stale-id warning with the recovery action ('re-read the list') is exactly the kind of operational context annotations cannot convey.

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?

Two sentences, front-loaded with what the tool returns and then the failure mode, with no filler. The long parenthetical stacks three separate id caveats in one clause, which is dense but each detail earns its place.

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 shape need not be described, and the description instead covers the two things an agent would otherwise get wrong: id scoping and the 404 path for foreign or merged ids. For a single-parameter read tool this is close to complete, with only the explicit use-case versus sibling read tools missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single entity_id integer, so the description must carry the meaning, and it does: ids are per-account and per-environment, must come from the monitoring list, and old ids of merged ABN entities are dead. It does not state the id's format or origin tool name beyond 'the list', but the key semantic constraints are supplied.

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 it returns 'One monitored entity' and contrasts that with the list variant by pointing to list_monitored_entities, so an agent can tell this is the single-record fetch versus the catalog call. The verb is only implicit ('One monitored entity' rather than 'Retrieves one monitored entity'), which keeps it just short of a 5.

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?

Guidance is indirect: the agent is told to consult list_monitored_entities for the object shape and to 're-read the list' when a stale merged id 404s, which implies the practical retrieve-then-fetch workflow. However, there is no explicit statement of when to use this versus siblings such as get_entity_snapshot or get_monitoring_event, so the choice is left to inference.

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