Skip to main content
Glama

Ask Monity to check an update

request_verification

Verifies a recent tracker update by having Monity open the linked page and confirm it matches the report, returning whether it is verified, unconfirmed, or inaccessible within minutes.

Instructions

Ask Monity to open the page an update from one of your tracker's connected agents names and check that it says what the update reports (needs a network:publish key): the update then shows Verified by Monity, or that Monity could not confirm it or could not open the page, usually within a few minutes. For an update posted in the last day. It counts as one check on your plan, within daily limits; its alerts are not sent again. A verified update stays verified.

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": {
      "update": "<update>"
    },
    "name": "request_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
updateYesThe update id (publicId, from get_network_changes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: auth requirement (network:publish key), cost (counts as one check against plan/daily limits), latency (usually within a few minutes), side effect (alerts not resent), and outcomes (verified / could not confirm / could not open, and verification is sticky). It omits whether re-requests are possible after a failure, but overall disclosure is rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded, but the run-on sentences, stacked parentheticals, and mid-string clauses ('needs a network:publish key', 'usually within a few minutes') make it harder to scan than necessary.

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?

For a single-parameter, no-output-schema tool with no annotations, the description covers the important context an agent needs: cost, timing, outcomes, and auth. Minor gaps (retry behaviour) remain but overall it is adequately complete.

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 coverage is 100% and the schema already explains the update id (publicId from get_network_changes). The description reinforces that the update must come from a connected agent's tracker but adds little format or sourcing detail beyond the schema, so baseline 3 applies.

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 action: open the page an update names and check that it says what the update reports, distinguishing it from passive reads like get_network_changes. The phrasing 'an update from one of your tracker's connected agents names' is a bit tangled, but the verb+resource is recoverable.

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 gives a clear usage constraint: 'For an update posted in the last day,' and notes the required network:publish key. It stops short of naming when to prefer a sibling such as get_network_update or update_monitor instead, so there is no explicit exclusion.

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