Skip to main content
Glama

trimtab-ais

by io.github.mrsingh86

Query a data series

query_series
Read-only

Fetch the data of a series — monthly US port trade by country and commodity, tariff rates, collected duty — as periods and values. Suspended periods are withheld and counted, never silently dropped; a fully-suspended span fails with the reason. Free, CC BY 4.0. No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclusive end
fromNoInclusive start, YYYY-MM-DD or YYYY-MM
limitNoMax rows, default 2000
seriesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYes
unitNo
gradeNo
seriesYes
citationNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "citation": {
+      "type": "string"
+    },
+    "grade": {
+      "type": "string"
+    },
+    "rows": {
+      "items": {
+        "properties": {
+          "period": {
+            "type": "string"
+          },
+          "value": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "period"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "series": {
+      "type": "string"
+    },
+    "unit": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "series",
+    "rows"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, and the description adds meaningful behavior beyond them: suspended periods are 'withheld and counted, never silently dropped,' and a fully-suspended span 'fails with the reason.' It also discloses licensing, cost, and authentication requirements, which is useful operational context.

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?

Three sentences, each carrying distinct value: what the tool returns, how suspension is handled, and access constraints. The core behavior is front-loaded and there is no filler or repetition of schema details.

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 an output schema present and annotations covering safety, the description adds the critical behavioral edge case (suspended periods) and access requirements. It does not describe parameter interactions like pagination or date-range formatting, but those are either in the schema or minor for a read-only fetch tool.

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?

Schema description coverage is 75%, so most parameter meanings are already in the schema. The description adds that results are 'periods and values' but does not explain the core 'series' parameter beyond the tool name, nor clarify how to/from/limit relate to the series output beyond what the schema already states.

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 states a clear verb ('Fetch') and resource ('data of a series'), and enumerates what the series contains ('monthly US port trade by country and commodity, tariff rates, collected duty') and its output shape ('periods and values'). It does not explicitly contrast with sibling tools like trade_query, but the content detail makes the purpose specific and identifiable.

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

Usage Guidelines2/5

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

The description gives no guidance on when to prefer query_series over any of its 12 sibling tools, nor does it describe exclusions or alternatives. The free/CC BY/no-key notes are access facts, not usage selection guidance, so the agent is left to infer suitability from the purpose alone.

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

All trimtab-ais toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Several tools overlap significantly in the tariff/trade domain: tariff_story explicitly replaces hs_search, tariff_lookup, and tariff_burden, and trade_query also returns duty data. This creates ambiguity about which tool to invoke for a given tariff question, though non-tariff tools (compare, event_studies, month_in_review) are clearly distinct.

Naming Consistency2/5

Tool names follow mixed conventions: some are verb-first (compare, query_series, tariff_lookup), others are noun-first (commodity_profile, tariff_burden, event_studies), and there's no consistent prefix or verb pattern. While readable, the lack of a unified naming scheme makes the set feel less coherent.

Tool Count4/5

With 13 tools, the set is within a reasonable range for a trade data service and covers most query needs. It's slightly larger than necessary given the overlapping tariff tools, but not excessive.

Completeness4/5

The surface covers tariff lookup, actual duties paid, trade volumes, comparisons, profiles, event studies, and rulings search, which is comprehensive for a read-only trade data resource. Minor gaps exist (e.g., no tool for gateway-specific tariff burden, and the meta-tool ledger_meta hides a set of archived tools), but core workflows are well supported.

Resources