Skip to main content
Glama

See what changed on problems and topics you follow

get_changes
Read-only

What changed since a cursor on the problems, topics or requests you name (request ids go in topic_ids). Use the cursor from the last call, get_problem, get_topic or get_request. There is no stream of everything new: name what you follow (list_my_entries finds your own).

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

Input Schema

NameRequiredDescriptionDefault
sinceNoCursor from an earlier result. Omit to get everything.
topic_idsNoTopics (top_) or requests (req_) to check. Up to 50 ids in all, with problem_ids.
problem_idsNoProblems to check. Up to 50 ids in all, with topic_ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic_ids / description
      Previous value: -"Discussion topics to check (ids starting top_). Up to 50 ids in all, with problem_ids."New value: +"Topics (top_) or requests (req_) to check. Up to 50 ids in all, with problem_ids."
  2. Changed4 schema fields changed
    • changedInput schema / properties / problem_ids / description
      Previous value: -"The problems to check, 1 to 50 ids."New value: +"Problems to check. Up to 50 ids in all, with topic_ids."
    • removedInput schema / properties / problem_ids / minItems
      Removed value: -1
    • addedInput schema / properties / topic_ids
      Added value: +{
      +  "description": "Discussion topics to check (ids starting top_). Up to 50 ids in all, with problem_ids.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "problem_ids"
      -]New value: +[]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the meaningful constraint that there is no all-encompassing new-items stream, which shapes how an agent must call it. It says nothing about pagination, result ordering, or whether the returned cursor is included in the response, and there is no output schema to cover that.

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?

Three compact sentences, front-loaded with what the tool returns and the id routing caveat. Every sentence carries distinct information and nothing is repeated from the schema.

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?

For a read-only, optional-parameter query tool this covers the essentials: scope, cursor sourcing, and the absence of a global feed. The gap is the return shape, since there is no output schema, so the agent cannot anticipate what a change record looks like or how to page forward.

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%, so the baseline of 3 applies. The description does add real meaning beyond the schema by clarifying that request ids belong in topic_ids and that the cursor should come from a prior result, but the combined 50-id cap across both arrays is only in the schema.

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?

The description states a specific verb and resource: it returns what changed since a cursor on problems, topics or requests. It also disambiguates the shared id parameter ("request ids go in topic_ids"), which no sibling name or schema field makes obvious.

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 tells the agent where to get the cursor (last call, get_problem, get_topic, get_request) and names list_my_entries for discovering what you follow. It also rules out a global feed. What it lacks is any explicit statement of when to prefer this over e.g. list_notes or get_telemetry for change tracking.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources