Skip to main content
Glama

LrrK Agent Desk

Check reviewed LrrK updates

lrrk_check_updates
Read-onlyIdempotent

Get exact record additions, corrections, and withdrawals between saved published version keys and the current public versions. Follow nextPage with the same knownVersions before saving the new keys. An unknown checkpoint or unavailable source means the exact comparison is incomplete.

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

Input Schema

NameRequiredDescriptionDefault
changePageNoCopy a source's nextPage exactly and keep the original knownVersions.
knownVersionsNoVersion keys from an earlier response. Omit on the first check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds real behavioural context beyond that: pagination via nextPage, the requirement to preserve knownVersions across pages, and the failure mode where an unknown checkpoint or unavailable source makes the comparison inexact rather than empty — a distinction an agent would otherwise get wrong.

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?

Three dense sentences with the core operation front-loaded, followed by pagination and then the failure caveat. No filler, though the second sentence packs multiple instructions and could be split for faster scanning.

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?

With no output schema, the description has to carry the return contract, and it largely does: it names the change categories, the nextPage continuation token, and the new keys to persist. What it does not state is the response shape for the change records themselves or how to detect the final page.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 and the field-level docs do the detail work. The description nevertheless adds lifecycle meaning the schema does not: knownVersions represents saved published keys from a prior response, must be reused while paging, and should only be replaced once the new keys are saved.

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 names a specific verb and a highly specific resource: additions, corrections and withdrawals between saved published version keys and current public versions. That is enough for an agent to recognise it as a checkpoint/diff tool rather than an evidence lookup, though no sibling is named to sharpen the contrast.

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?

It supplies procedural guidance — follow nextPage with the same knownVersions before saving the new keys — which implies the intended workflow, and the schema notes knownVersions is omitted on the first check. There is still no explicit statement of when to reach for this tool instead of the find/get evidence siblings.

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