Skip to main content
Glama
Sign In
SupplyMaven API Pro

SupplyMaven API Pro

Official
by SupplyMaven-SCR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_customs_friction_baseline

Assess customs clearance risk with a composite score combining port congestion and trade policy events for 21 countries.

Instructions

Get customs friction baseline scores by country. Returns a composite 0-100 score combining port congestion (55% weight) and customs/trade policy events (45% weight). Covers 21 countries across North America, East Asia, Southeast Asia, South Asia, Europe, Middle East, and South America. Higher score = more friction. Optional country parameter for single-country detail with component breakdown and 30-day history. Used by trade compliance teams, procurement managers, and logistics planners to assess customs clearance risk by country.

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": "get_customs_friction_baseline"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations, so description carries burden. It discloses scoring weights, country coverage, score direction, and optional parameter behavior. However, it mentions an optional country parameter not present in the input schema, which could mislead an agent about tool capabilities.

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 concise, well-front-loaded sentences. Each provides distinct value: purpose, data composition, and use audience. No redundancy.

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?

Covers what is returned (composite score, components, history), coverage scope (21 countries/regions), and intended users. Lacks explicit output format for multi-country queries and parameter syntax for the claimed optional country filter, but sufficient for a high-level understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has zero parameters, baseline 4, but description claims an optional country parameter. This is a schema contradiction. The description adds misleading information about a parameter that does not exist in the schema, so it fails to provide accurate semantic guidance.

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?

States clearly it retrieves customs friction baseline scores by country, with explicit composite scoring methodology (55% port congestion, 45% policy events), distinguishing it from related tools like get_customs_trade_events and get_port_congestion_trends.

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?

Targets trade compliance, procurement, and logistics audiences and explains the score's meaning (higher = more friction), implying use cases. Does not explicitly contrast with alternatives or state when not to use, but provides sufficient context.

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