Skip to main content
Glama

Recent changes

get_changes

What changed in Lode records, newest first: prices, sync capabilities, limits, regions and verification status. Each event has the old and new value, when Lode observed it, the sources behind it and a cause (new-coverage, lode-update, or source-change-likely when the cited page also changed).

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
idNoIntegration id "{app}--{ecosystem}"
limitNo
sinceNoISO date, e.g. "2026-11-01"
ecosystemNoEcosystem slug, e.g. "vercel"
include_new_coverageNoInclude "added to Lode" events (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does substantial work: it discloses the ordering ('newest first'), the per-event payload (old value, new value, observation time, sources), and the cause taxonomy including the notable edge case 'source-change-likely when the cited page also changed'. It omits read-only confirmation, result-size/pagination behavior, and default time window, which keeps it short of a 5.

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 sentences, front-loaded with the core answer ('what changed, newest first') before the payload detail. The second sentence is dense but every clause (old/new value, observed time, sources, cause values) conveys distinct information an agent would otherwise have to discover by calling the tool.

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 5-parameter, zero-required read tool with no output schema and no annotations, the return-value description is strong, but filtering behavior is left entirely to the schema — no explanation of how limit interacts with a change feed, what happens when since is omitted, or how include_new_coverage changes the result set. An agent can call it, but not predict result volume or filtering precisely.

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 80%, so the schema already documents id, since, ecosystem and include_new_coverage. The description adds only indirect meaning — explaining the 'new-coverage' cause, which loosely maps to the include_new_coverage flag — and says nothing about limit semantics or the relationship between since and the default window. Baseline 3 is appropriate.

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 states a specific resource and scope: 'What changed in Lode records, newest first', then enumerates the record dimensions tracked (prices, sync capabilities, limits, regions, verification status). It is clearly distinct from siblings like get_integration or compare_integrations, but it never names an alternative or explicitly contrasts its scope with them.

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 only implied: the phrase 'what changed ... newest first' suggests a change-feed/changelog use case, and the mention of old/new values implies audit-style queries. There is no explicit when-to-use instruction, no statement of when to prefer get_integration or compare_integrations instead, and no prerequisites or exclusions.

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