Supply-chain stress index — CBP BWT + GDELT chokepoint mentions + AIS/MarineTraffic hint, port congestion for freight/commodity/middle_east Polymarket edge.
| Name | Required | Description | Default |
|---|---|---|---|
| ports | No | Ports e.g. LAX,NYC,HOU,LGB | |
| chokepoints | No | Chokepoints e.g. hormuz,bab-el-mandeb,suez,bosphorus |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are empty, so the description must disclose behavioral traits. It lists data sources but does not state whether the tool is read-only, what side effects exist, or any permissions required. It hints at return (an index) but lacks details on behavior like frequency of update or error conditions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that packs in multiple data sources and use cases, making it somewhat dense and jargon-filled. It could be more readable and structured to convey the same information more clearly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Without an output schema, the description does not explain the return format (e.g., what an 'index' looks like) or whether parameters are required. It mentions a 'hint' but lacks completeness on how to interpret results. For a tool with two optional parameters, the description provides minimal guidance.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both parameters (ports and chokepoints). The description adds value by providing concrete examples: 'Ports e.g. LAX,NYC,HOU,LGB' and 'Chokepoints e.g. hormuz,bab-el-mandeb,suez,bosphorus', which help the agent understand valid inputs beyond the schema text.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides a supply-chain stress index composed of specific data sources (CBP BWT, GDELT, AIS/MarineTraffic, port congestion) and ties it to Polymarket edge for relevant markets. It names the resource and implies the verb (get/index), but does not explicitly differentiate from sibling tools like marine_conditions or mcp_supply_chain_iocs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives. The description mentions a Polymarket edge but does not specify when this index is preferred over other supply chain tools or what types of queries it serves best.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools cover very diverse domains (weather, FDA, legal, crypto, etc.), so cross-domain confusion is low. However, within domains there is notable overlap: multiple food recall tools (food_recall_check, food_safety), multiple weather tools (weather_current_global, weather_forecast_grid, weather_alerts, weather_bias), and several Polymarket-related tools. This can cause agent misselection.
Naming is inconsistent: some tools use verb_noun (search_arxiv, scrape, validate_agent_manifest), others use noun phrases (smart_money, space_weather, tide_data), and some are long descriptive phrases (cross_platform_arb_scan, polymarket_event_scan). No single pattern is followed, making predictions difficult.
95 tools is excessively high for any coherent purpose. The server appears to be a random aggregation of APIs with no clear scope. Such a large catalog overwhelms agents and dilutes utility; most tools could be split into specialized servers.
Although many domains are touched, each is covered only shallowly. For example, weather lacks historical data, legal lacks case details beyond court opinions, and financial lacks stock prices. There are obvious gaps like no user authentication or data persistence. The tool set feels like a collection of endpoints rather than a cohesive service.