Skip to main content
Glama

watch_updates

Read a configured profile's current watch run to inspect source failures and untrusted notice events without refreshing sources or consuming events.

Instructions

Read the latest watch run for a configured profile, including source failures and untrusted notice events.

Reading this tool neither refreshes sources nor consumes events.

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": {
      "profile": "<profile>"
    },
    "name": "watch_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
profileYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 disclosure burden and does a good job on the key axis: it explicitly states there are no side effects (no source refresh, no event consumption). What it omits is whether the profile must already be configured, what happens if no run exists, and any pagination behavior — smaller but real gaps.

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?

Two tight sentences, both of which earn their place: the first states what is returned, the second rules out side effects. No filler or repetition.

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

Completeness3/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-value explanation is appropriately delegated. However, for a tool with three undocumented parameters and no annotations, the description leaves pagination semantics and the no-run case unaddressed, which an agent would need to call it confidently.

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% across three parameters, so the description must compensate. It only clarifies 'profile' as a configured profile and says nothing about limit or offset, leaving the pagination parameters entirely undocumented in both places.

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 gives a specific verb and resource: read the latest watch run for a configured profile. It also names what the result contains (source failures and untrusted notice events). It doesn't explicitly name a sibling like refresh_status or start_refresh, but the phrasing strongly hints at that distinction.

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?

Usage is only implied: the statement that reading 'neither refreshes sources nor consumes events' signals this is a pure inspection call rather than a refresh trigger. There is no explicit 'use this when...' or a named alternative for when the agent wants to start or check a refresh.

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