Skip to main content
Glama

Summarise what changed

summarize_network_changes

Summarizes recent changes on a Monity Network tracker or entire site from change records, citing evidence for each statement. Returns null when no changes can be reported.

Instructions

A short summary of what changed on a tracker or a whole site over the last days ("this week Notion changed its pricing page twice: Team from $10 to $12 [1, 2]"), written only from Monity Network change records; every sentence cites records listed in citations. text is null when nothing changed or nothing could be said from the records.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "summarize_network_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo7 (default) or 30; any other number reads as 7
siteNoA site, e.g. notion.so
watchNoA one-source tracker's slug or id
watchlistNoA tracker's slug or id, for a tracker with several sources

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does a fair job: it declares the data source ('written only from Monity Network change records'), a hard citation requirement for every sentence, and the null-text outcome when nothing changed. It does not state read-only safety, latency, or cost, but the substantive output semantics are disclosed.

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?

It is a single dense sentence, but it is front-loaded with the core purpose and the inline example earns its place by showing the citation format. Slightly packed with parenthetical example text, yet nothing is redundant.

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?

There is no output schema, so the description must convey the return shape, and it does the important part: 'text' plus a 'citations' list, and when text is null. It stops short of describing the full response object or how citations are keyed, which is a minor gap for a four-parameter read tool.

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 description coverage is 100%, so the schema already explains days (default 7, capped at 90), site, watch, and watchlist. The description only adds the loose framing 'on a tracker or a whole site over the last days' and adds no new meaning about how watch vs watchlist differ or how they interact.

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 ('a short summary of what changed on a tracker or a whole site') and even supplies a worked example of the output, so the agent knows this produces synthesized prose rather than raw records. It implicitly separates itself from record-listing siblings by saying it is 'written only from Monity Network change records', but it never names the raw-record alternative explicitly.

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 implied rather than stated: the agent can infer this is the tool for a narrative digest over a recent window, and the example plus 'over the last days' anchors the typical case. There is no explicit when-not guidance or pointer to get_network_changes / query_network_records for unsummarized data, so the routing decision 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.