Skip to main content
Glama

Redstick: construction tech on the record

What changed since a date (paid)

what_changed
Read-only

What changed on Redstick's record since a date: every tool whose record changed, in full, with those changes. Paid per call by x402 in USDC: $0.05 a call including the first 10 tools returned, then $0.02 for each further tool (the most a call can cost, at 200 tools, is $3.850); set limit to hold the cost. The exact price is stated before anything is paid. A call that cannot be answered as asked, or that finds nothing, is free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "since": "<since>"
    },
    "name": "what_changed"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNoa job's slug, from list_jobs
kindNorobot, saas or ai-tool
limitNo1 to 200, default 50
sinceYesYYYY-MM-DD: tools whose record changed on or after this date, with those changes
tradeNoa trade's name, from list_trades
offsetNodefault 0
countryNotwo-letter country code where the tool is sold, e.g. GB
works_withNoa system's slug, from list_systems
maker_countryNothe maker's country by name, e.g. Germany

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: it discloses the x402 USDC billing model, the $0.05 base including 10 tools, $0.02 per additional tool, the $3.85 worst case at 200 tools, that price is quoted before payment, and that empty or unanswerable calls are free. It also points to `limit` as the cost-control lever — exactly the kind of consequence an agent needs before invoking a paid call.

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?

Purpose is front-loaded in the first clause, with cost/billing following in a logical order. The pricing arithmetic is a little dense but each figure carries real decision value, and there is no filler.

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?

For a 9-parameter tool with no output schema, the definition covers purpose, cost, and result scope adequately, and the filters are fully self-documenting in the schema. It stops short of describing pagination behavior via `offset` or how the change sets are structured in the response.

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; the description exceeds it by giving `limit` an economic meaning ('set limit to hold the cost') that the schema's bare '1 to 200, default 50' does not convey. The other eight filters are left entirely to the schema.

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?

Names a specific resource (Redstick's tool records) and a specific question (what changed since a date), plus the scope of the return ('every tool whose record changed, in full'). It is distinguishable from siblings like search_tools or get_tool, though it never explicitly contrasts itself 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?

The `since` framing implies when to reach for this tool (change-tracking over a date window), but there is no explicit guidance on when to prefer query_record/get_tool/search_tools instead, and the optional filters' role in narrowing results is left unstated.

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