Skip to main content
Glama

TradieBridge

by com.tradiebridge
OverviewDiscussionsAdmin

Search records

search_records
Read-only

Find records of one resource in a source's backup, whatever the system, highest source ID first, or largest first by order_by (ascending: true for smallest or oldest; empty values last). query matches a source ID as a prefix or a name holding every word; filters and order_by take the columns describe_resources lists. Answers the total that match and, when more remain, next_before_id to pass back as before_id (with order_by, raise limit instead). Each result's id is what get_record takes. For totals and counts use summarize_records instead of paging.

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25, at most 200.
queryNo
filtersNoColumn filters, from the columns describe_resources lists for the resource: {"<column>": "value"}, {"<column>": ["one", "another"]}, {"<column>": {"contains": "acme"}}, {"<date column>": {"gte": "2026-04-01", "lte": "2026-06-30"}}. Operators: eq, ne, in, not_in, gte, lte, contains, null.
order_byNoA number or date column describe_resources lists, to rank by.
resourceYesA resource key from describe_resources, e.g. invoices.
ascendingNo
before_idNoThe next_before_id a previous page answered.
connection_idNoOmit when only one of the company's sources holds the resource; list_connections names them.
modified_sinceNoISO 8601 time; only records the source changed since then.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / build_id
      Removed value: -{
-  "description": "Omit when only one of the company's builds holds the resource; list_connections names them.",
-  "type": "integer"
-}
    • addedInput schema / properties / connection_id
      Added value: +{
+  "description": "Omit when only one of the company's sources holds the resource; list_connections names them.",
+  "type": "integer"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, not open-world), and the description adds genuinely new behavior: default ordering (highest source ID first, empty values last), ascending semantics, and the pagination contract (next_before_id returned and fed back as before_id). It stops short of mentioning permissions, rate limits, or ordering stability across pages.

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 and ordering lead, then matching, pagination, and routing to siblings — a well front-loaded order with no filler. The sentences are dense and occasionally run-on (multiple parenthetical clauses), which slightly slows parsing.

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

Completeness5/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 carries the return contract itself (total matches, next_before_id, per-result id) and covers the pagination and ordering knobs for a 9-parameter tool. Nothing essential to invoking or correctly paging this tool is missing.

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 78%, so the baseline is 3, but the description adds real meaning beyond the schema for query (source-ID prefix or name matching every word), ascending (smallest/oldest direction), and before_id (round-trip from next_before_id). It does not clarify modified_since or connection_id beyond the schema's own wording.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find records of one resource in a source's backup, whatever the system') with its default ordering rule. It distinguishes itself from siblings by explicitly naming summarize_records and get_record and describing how results chain into them.

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

Usage Guidelines5/5

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

Gives explicit when-not guidance ('For totals and counts use summarize_records instead of paging') and when-to guidance for downstream consumption ('Each result's id is what get_record takes'). It also explains the alternative path when order_by is set ('raise limit instead' of paging).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TradieBridge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources