Skip to main content
Glama
Sign In
xippios-mcp

xippios-mcp

by xippios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

comtrade_get_live_update

Read-onlyIdempotent

Lists 50 recent UN Comtrade release-pipeline entries in reverse chronological order to monitor dataset releases and their status.

Instructions

List the 50 most recent releases in UN Comtrade's release pipeline, newest first.

Upstream's getLiveUpdate: for each release the reporter (reporter_code, a string here, e.g. "842"), type_code, freq_code, classification_code, period, file size, status and release_status (e.g. "Released"), and four times: started_at and completed_at (UTC), last_updated (a day) and queued_at (no zone given, kept naive). There is no publication date field; get_data_availability and get_metadata carry those per dataset. One call, no arguments. Upstream's count (174 when recorded) is not the number of rows, so it is not returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "comtrade_get_live_update"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses the 50-row cap, newest-first ordering, that there is no pagination or filtering, and the exact per-release fields returned. It even flags data-quality quirks an agent would otherwise misread, such as queued_at being naive with no zone and upstream's count not being the row count.

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?

The scope and ordering constraint are front-loaded in one sentence, and the field inventory follows efficiently. The closing aside about upstream's count is a minor detour, though it does preempt a likely misreading.

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 full burden of describing return values and does so field by field, including time semantics and the absence of a publication date. Nothing an agent needs in order to call this zero-argument tool and interpret the response 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?

The tool takes no parameters, so the baseline is 4 and there is nothing for the description to clarify on the input side. Its field-level detail describes outputs rather than parameters, which is useful but does not raise this dimension further.

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 first sentence gives a specific verb, resource, scope and ordering: 'List the 50 most recent releases in UN Comtrade's release pipeline, newest first.' It also implicitly separates itself from the release-listing sibling by noting that publication dates live in get_data_availability and get_metadata rather than here.

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

Usage Guidelines4/5

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

It states the calling contract plainly ('One call, no arguments') and routes the agent to get_data_availability and get_metadata when publication dates are needed. What it does not do is distinguish this from comtrade_get_comtrade_releases, so the agent must infer which of the two release tools to pick.

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

Deploy Server

Other Tools