Skip to main content
Glama

Redstick: construction tech on the record

Search the record

search_tools
Read-only

Search Redstick's dated record of construction robots, software and AI tools by words, job, trade or kind. Free. Returns up to 10 tools a call, each with what it does, who it suits, the catch and the price as the maker states it.

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

Input Schema

NameRequiredDescriptionDefault
qNowords to look for in a tool's name, maker, description, trades and jobs
jobNoa job's slug, from list_jobs
kindNorobot, saas or ai-tool
limitNo1 to 10, default 5
tradeNoa trade's name, from list_trades
offsetNodefault 0

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=true and openWorldHint=false, and the description adds genuinely useful context on top: no cost, a 10-result-per-call ceiling, and the per-result fields (what it does, who it suits, the catch, the price as stated by the maker). It stops short of explaining result ordering or how to page past the first 10, which matters given the offset parameter.

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?

Two compact sentences with no filler, and the core capability is front-loaded before the result-shape detail. Every clause carries information an agent can act on.

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 six-parameter, zero-required search tool with full schema coverage and no output schema, the description covers purpose and result contents well. The remaining gap is paging and ranking behavior across multiple calls, which the offset parameter implies but the text does not explain.

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 all six parameters are already documented, including the job/trade slug sources and the 1-10 limit. The description's 'by words, job, trade or kind' loosely mirrors the q/job/trade/kind parameters and 'up to 10 tools a call' restates the limit, adding little beyond the schema; limit/offset paging semantics 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?

The description gives a specific verb and resource ('Search Redstick's dated record of construction robots, software and AI tools') plus the dimensions searched (words, job, trade, kind). It is clear enough to distinguish from get_tool, but it never names a sibling, so the boundary against query_record or the list_* tools must be inferred.

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: 'search by words, job, trade or kind' tells the agent the available entry points but gives no when-to-use versus query_record/get_tool or any exclusion. 'Free' and 'up to 10 tools a call' hint at the cost and paging model, but nothing states when this tool is the wrong 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