get_recent_changesPages edited within the last N days, newest first — what to poll when you are watching the wiki rather than reading it. Same row shape as list_pages. Look back at most 30 days and take at most 50 rows; for anything older, list_pages sorted by updatedAt.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Look back N days (default 7, max 30) | |
| limit | No | Max results (default 20, max 50) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnly and idempotent annotations, the description discloses the row shape ('Same row shape as list_pages'), ordering ('newest first'), and hard limits (max 30 days, max 50 rows). This is more behavioral detail than typical and helps the agent predict results accurately.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences front-load the core behavior and then add purpose, output compatibility, and limits. Every phrase earns its place without repetition or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers purpose, usage context, limits, ordering, and row shape in a compact form. Combined with full parameter schema coverage and readOnly/idempotent annotations, nothing important is missing for a correct call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameters are already fully documented in the schema. The description restates the 30-day and 50-row caps but does not add new semantic meaning beyond what the schema provides, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states a specific verb and resource: pages edited within last N days, newest first. It distinguishes itself from list_pages by framing itself as the polling tool for watching the wiki rather than reading it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use it ('what to poll when you are watching the wiki') and names the alternative for older data ('for anything older, list_pages sorted by updatedAt'). This gives the agent clear routing guidance with no inference needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.