Skip to main content
Glama

Redstick: construction tech on the record

Systems tools connect to

list_systems
Read-only

The systems and file formats that tools on Redstick's record say they connect to, with how many tools name each. Free. Without q, only systems named by three or more tools.

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

Input Schema

NameRequiredDescriptionDefault
qNopart of a system's name, e.g. revit
min_toolsNoonly systems named by at least this many tools; default 3, or 1 with q

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: the call is 'Free' (no quota/cost) and that without q results are restricted to systems named by three or more tools. It says nothing about ordering or result size, so it is additive but not rich.

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 short sentences, the returned content front-loaded ahead of the filtering caveat. The fragment 'Free.' is slightly telegraphic but carries real information; nothing is redundant.

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 zero-required-parameter, read-only listing tool with no output schema, the description covers what the entries are and the count they carry, plus the default filtering threshold. Only result ordering and rough cardinality are unstated.

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 both parameters are already documented including the default-3 / 1-with-q rule. The description reinforces the min_tools default behavior in prose and pairs it with the q exception, which gives an agent the practical takeaway (a bare call is a popularity-filtered view) without needing to read 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 names a specific resource — systems and file formats that tools on the record connect to — plus what each entry carries ('how many tools name each'). That distinguishes it from search_tools, list_jobs and list_trades by resource. It lacks an explicit verb ('list') and any direct sibling reference, so it falls short of a 5.

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: an agent can infer this is a browse/taxonomy endpoint and that supplying q narrows it. There is no explicit statement of when to call this versus search_tools or query_record, and no guidance on when the unfiltered view is preferable.

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