Skip to main content
Glama

Trustbase Lab · rCB & Chemical Recycling Data

by com.trustbaselab
OverviewDiscussionsAdmin

Trade Dataset Overview

get_trade_dataset_overview
Read-onlyIdempotent

Purpose: describe the trade flow dataset - source, caliber, unit conversion, derived-field declarations, fieldtable and compliance boundaries - so an agent can cite and interpret it correctly. Guidelines: call this beforerunning any trade query that will be quoted; it states explicitly which fields are customs-reported and whichare our own derivations. Limits: UN Comtrade official statistics only - no commercial quote platform data entersthis dataset; this tool documents the dataset and returns no trade records itself. Ex:get_trade_dataset_overview(), get_trade_dataset_overview(response_format='json').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (machine-readable).markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesHuman-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / response_format / description
      Added value: +"Output format: 'markdown' (default, human-readable) or 'json' (machine-readable)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "text": {
+      "description": "Human-readable result (markdown, or a JSON string when response_format=json).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already signal readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond those flags: the dataset is UN Comtrade official statistics only, fields have customs-reported versus derived declarations, and the call itself is documentation-only, returning no trade records.

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?

The description is well structured with Purpose, Guidelines, Limits, and Ex sections. The core purpose is front-loaded, each section earns its place, and the examples are compact and useful.

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 one optional parameter, an output schema, and strong annotations, the description supplies all necessary invocation context: what the tool documents, when to call it, its data-source limits, and what it will not return. Nothing needed for correct use is missing.

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?

The input schema has 100% coverage for response_format, including enum values, default, and description. The description only adds call examples rather than new semantic meaning for the parameter, so it stays at the baseline 3 for high schema coverage.

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?

The description opens with a specific verb and resource: 'describe the trade flow dataset.' It then lists concrete content categories (source, caliber, unit conversion, derived-field declarations, compliance boundaries) and explicitly states it returns no trade records, distinguishing it from query/data-retrieval tools among siblings.

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?

The guidelines explicitly say to call this before any trade query that will be quoted seems an exact when-to-use instruction. It also states the tool returns no trade records and that only UN Comtrade official statistics are involved, giving agents clear boundaries for when not to rely on it.

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

All Trustbase Lab · rCB & Chemical Recycling Data 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