Skip to main content
Glama

TradieBridge

by com.tradiebridge
OverviewDiscussionsAdmin

Get records

get_record
Read-only

Records from a source's backup, whatever the system, exactly as the source sent them, with the records each one names (links) and the records hanging off it (related, first 50 of each). id is the source's own ID, or the id search_records returned; ids reads up to 20 at once. fields keeps only those keys of each document: top-level keys or dotted paths such as Contact.Name.

Input Schema

NameRequiredDescriptionDefault
idNo
idsNoSeveral ids, instead of id.
fieldsNoKeys or dotted paths to keep, e.g. ["Name", "Contact.Name"].
relatedNoDefault true. False leaves out links and related records.
resourceYesA resource key from describe_resources.
connection_idNoOmit when only one of the company's sources holds the resource; list_connections names them.

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: records are returned raw, links and related records are included with a 'first 50 of each' truncation disclosure, and fields filtering behavior is described.

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?

It is dense and front-loaded with the return shape before parameter behavior. The single run-on paragraph packs multiple ideas via parentheticals, which is efficient, though it borders on unwieldy for a first read.

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?

With no output schema, the description carries the return-value burden and does so by explaining raw record content, links, related records, and the 50-item cap. Combined with high schema coverage on inputs, an agent has enough to invoke it correctly, with only minor gaps around the singular/plural id interplay.

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 83%, so the schema already documents most parameters, which sets a baseline of 3. The description adds value beyond the schema by clarifying that 'ids reads up to 20 at once' and that id is the source's own ID or one returned by search_records, neither of which is stated in 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 conveys a specific resource and its retrieval semantics: raw records from a source's backup 'exactly as the source sent them,' plus links and related records. It is clearly distinguishable from search_records, whose returned ids it references. The only minor gap is that the noun-phrase opener leads with what is returned rather than an explicit verb.

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?

It implies a workflow by noting that 'id is the source's own ID, or the id search_records returned,' giving an implicit routing hint to search_records. However, it never states when to prefer get_record over summarize_records or the read/write operation tools, and gives no exclusions.

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