Skip to main content
Glama

recent_changes

Read-only

Lists recent human and AI edits to a circuit board newest first, including undos and redos, so you can review changes and resume from a specific edit.

Instructions

List recent changes by you and the human, newest first, with undos and redos. id: what one change did; since: all after it.

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

Input Schema

NameRequiredDescriptionDefault
idNo
limitNo
sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered by structured data. The description adds genuine behavior beyond that: result ordering (newest first), inclusion of undo/redo entries, and default scoping to the current user plus 'the human'. It says nothing about default page size, how 'limit' interacts with 'since', or result shape.

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 short sentences, front-loaded with scope and ordering before the parameter hints; nothing is redundant. The telegraphic 'id: ...; since: ...' style buys brevity at some cost in readability.

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 list tool with no output schema, the agent still lacks the return shape, the accepted timestamp format for 'since', the default and maximum result count, and overload behavior when both filters are passed. What is present is accurate, but not enough to call the tool confidently without extra probing.

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%, so the description carries the full burden for three parameters. It explains 'id' and 'since' only telegraphically (no format for the 'since' string, no statement of what 'id' expects), and 'limit' — with its 1-200 range — is not mentioned at all.

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?

States a specific verb and resource ('List recent changes'), plus scope ('by you and the human'), ordering ('newest first') and that undos/redos are included. The purpose is unmistakable, though it names no sibling to differentiate against (the siblings are unrelated drawing tools, so that gap is low-impact).

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?

The clause 'id: what one change did; since: all after it' gives the agent a clear selection rule between the two filtering modes. It stops short of exclusions or prerequisites (e.g. whether it needs an authenticated session, or what happens if both id and since are supplied).

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