Skip to main content
Glama

Market change summary

get_change_summary
Read-onlyIdempotent

Get counts of U.S. market events over the last 1-30 days (new listings, price cuts and increases, sales, relistings, delistings), without returning individual properties. If the result has a 'note', pass it on to the user. Cheap — use this before get_recent_changes to size a question, or to answer 'how active is the market right now?'

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_change_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days of changes to summarize

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds meaningful context beyond that: results are aggregates only, the call is cheap relative to the sibling, and a 'note' field in the result must be surfaced to the user. It stops short of describing the actual count keys returned, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what it returns, then scope, then the agent-facing pass-through instruction and cost/routing advice. No filler; every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter aggregation tool with rich annotations and no output schema, the description covers return shape (aggregate counts, possible 'note'), usage routing, and cost. Nothing an agent needs in order to call it correctly is missing.

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% with a single 'days' integer bounded 1-30 and already defaulted; the description only restates the 1-30 day window and adds no new syntax or format detail. Baseline 3 applies when the schema carries the parameter meaning.

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?

States a specific verb and resource (counts of U.S. market events) and enumerates the event types covered, while explicitly scoping out individual property records — which separates it from get_recent_changes. An agent can pick this tool without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance with a named alternative: use before get_recent_changes to size a question, or to answer 'how active is the market right now?'. The 'without returning individual properties' clause implicitly rules out per-property use.

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