Skip to main content
Glama

Redstick: construction tech on the record

One tool in full

get_tool
Read-only

One tool from Redstick's record in full: the verdict, the source read, features, where it is sold and what it connects to, as it stands today. 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": {
      "slug": "<slug>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesthe tool's slug, as search_tools returns it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a read-only, closed-world operation, so the bar is lower. The description adds two useful behavioral notes—'as it stands today' signals a current snapshot rather than history, and 'Free' signals no billing cost—but says nothing about behavior for an unknown or stale slug.

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?

A single front-loaded sentence that leads with the resource and then lists the record's parts, with no redundant hedging. The trailing 'Free' is slightly abrupt but is real information rather than padding.

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

Completeness3/5

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

With no output schema, the description usefully enumerates the fields returned, which is the main completeness need for a single-record read. However, it omits not-found/staleness behavior and never references the slug input, leaving small but real gaps.

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?

There is a single required parameter and schema coverage is 100%, so the schema fully documents the slug. The description adds no additional meaning about slug format, case sensitivity, or resolution behavior, which is the expected baseline at full schema coverage.

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 verb (retrieve) and resource (one tool's full record) and enumerates the record's contents: verdict, source read, features, where sold, and connections. That is concrete and distinguishes a full detail fetch from a list/search, though it never names a sibling for contrast.

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: 'in full' suggests this is the detail lookup following a search, and the schema's slug note ('as search_tools returns it') reinforces the workflow. The description itself gives no explicit when-to-use, when-not, or alternative between this, query_record, and search_tools.

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