Skip to main content
Glama

AlpineDataWorks Intelligence Server

by com.alpinedataworks

Supply Chain Geopolitical Risk Index

adw.adw_354
Read-only

Returns a 0-100 US supply-chain geopolitical risk index (China import share 40% plus import-flow and trade-balance z-scores; monthly FRED/BEA bilateral trade data since 2002) with score, trend, top_drivers, and source_lineage. Call when the user asks about supply chain risk, China dependence, decoupling, reshoring, tariffs, or trade-war exposure, or when timing supplier diversification, procurement audits, or supply-chain due-diligence reporting. Updates: monthly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoOptional: return a daily HISTORY series of the last N days (up to 5 years of real archived data) instead of the current snapshot. History requires Gold tier; without it, the current snapshot is returned.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds valuable behavioral context: monthly updates, data sources (FRED/BEA), and the 40% China import share weighting. No contradictions found.

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 tightly packed sentences: output and methodology, when to use, and update cadence. Every sentence adds distinct value, and the most important information is front-loaded in the first sentence.

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?

For a read-only data tool with one optional parameter and no output schema, the description covers the return fields, methodology, update frequency, and usage scenarios. It lacks only explicit return-format examples, but the described output fields suffice for invocation.

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 coverage is 100% and the single optional 'days' parameter is fully described in the schema, including the Gold tier requirement. The main description does not repeat parameter details, so it neither adds nor detracts from the schema.

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 ('Returns') and identifies a concrete resource: a 0-100 US supply-chain geopolitical risk index. It details the index composition and outputs, making it clearly distinct from the many numbered sibling tools.

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?

The description provides explicit trigger phrases ('asks about supply chain risk, China dependence, decoupling, reshoring, tariffs, or trade-war exposure') and practical scenarios. It does not name alternative tools or state when not to use it, but the guidance is clear and actionable.

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

All AlpineDataWorks Intelligence Server 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

B3.3/5.0
Disambiguation1/5

With 318 tools named adw.adw_###, agents cannot tell them apart without reading full descriptions. Multiple tools cover the same domain (e.g., at least three USD strength scores: adw_055, adw_250, adw_580; four supply-chain stress scores: adw_009, adw_019, adw_020, adw_547), making misselection highly likely.

Naming Consistency3/5

The vast majority follow a consistent numeric ID pattern (adw.adw_###), but a small set breaks this with descriptive snake_case names (adw.catalog, adw.sample, adw.county_cancer, etc.). The numeric IDs are predictable but convey no semantic meaning, mixing with the few named tools and creating moderate inconsistency.

Tool Count1/5

318 tools is far beyond any reasonable scope for an intelligence server; even the largest sophisticated APIs rarely exceed 50. This extreme count suggests poor curation and will overwhelm agents with choice, making efficient tool selection impractical.

Completeness3/5

The server covers an extremely broad range of domains (crypto, macro, supply chain, healthcare, climate, county demographics), and includes discovery tools like adw.catalog and adw.sample. However, the surface is redundant and not systematically complete—many overlapping indices exist while other potentially valuable operations (e.g., raw data export, historical trend queries) are missing, leaving moderate gaps.

Resources