Skip to main content
Glama

Redstick: construction tech on the record

Query the record (paid)

query_record
Read-only

Redstick's record filtered by job, trade, kind, country sold in, maker's country or connected system, each tool in full with its dated log of 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

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

Input Schema

NameRequiredDescriptionDefault
jobNoa job's slug, from list_jobs
kindNorobot, saas or ai-tool
limitNo1 to 200, default 50
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

A3.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them with a full pricing model ($0.05 per call covering the first 10 tools, $0.02 per additional tool, $3.85 ceiling at 200 tools), a pre-payment price disclosure, and a free-call guarantee for unanswerable or empty results. That is exactly the kind of cost and failure-mode context an agent needs before invoking a paid tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose is front-loaded and the pricing block is genuinely useful, but the first sentence is a run-on that crams six filters and the return shape into one clause chain, and the parenthetical cost arithmetic is dense. It is information-rich rather than padded, but the structure could be far cleaner.

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 an 8-parameter, read-only, no-output-schema tool, the description covers the filter surface and the cost model thoroughly. It leaves offset/pagination behavior and the exact response shape unstated, which is a minor gap given the schema documents the parameters.

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 100%, so the schema already documents every parameter including the enum and the limit range. The description adds only one piece of meaning beyond it: that limit is the lever for controlling cost. Baseline 3 applies.

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 the resource (Redstick's record of tools) and enumerates the filter dimensions (job, trade, kind, country sold in, maker's country, connected system) plus what is returned ('each tool in full with its dated log of changes'). It is specific enough to distinguish a filtered bulk record from a single-item lookup, though the opening sentence is grammatically tangled and never states a clean verb.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance and no sibling is named, even though get_tool, search_tools and what_changed are obvious alternatives for overlapping needs. The only actionable guidance is cost-related ('set limit to hold the cost'), which tells the agent how to call cheaply but not when this tool is the right choice.

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