Skip to main content
Glama

TRIPWIRE incidents tagged with affected assets

get_incident_assets
Read-onlyIdempotent

Use this when you need recent geopolitical, conflict and natural-hazard incidents mapped to the asset classes and liquid proxies they are tagged against (oil, grains, gas, semis, gold, Treasuries, country ETFs). Free. License: cleared_with_attribution. Attribution required: The GDELT Project (https://www.gdeltproject.org/); Uppsala Conflict Data Program (UCDP), CC BY 4.0; U.S. Geological Survey; GDACS (EC-JRC / UN OCHA), not for life-safety use. Asset tagging by cev-os TRIPWIRE.

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_incident_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoCase-insensitive substring filter on asset tags, e.g. oil, semiconductors, gold.
regionNoRegion filter.
since_hoursNoIncidents updated in the last N hours (1-168, default 24).
min_severityNoMinimum severity 1-5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, and the description adds material context beyond them: it is free, cleared_with_attribution, requires specific attribution strings per source, and carries an explicit "not for life-safety use" caveat for GDACS data. That is genuine operational disclosure. It stops short of a 5 because freshness ("recent") is not quantified in the description itself and no volume or rate-limit behavior is mentioned.

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 use case is front-loaded in the first clause and the data scope follows immediately. The attribution and licensing tail is verbose but functionally necessary for compliant use, so it earns its place; the only waste is slight repetition of source listing.

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 four optional parameters, no required inputs, and no output schema, the description is adequately complete: it conveys what the records contain (incidents plus asset-class and proxy tags) and the licensing constraints. The one gap is default behavior when no filters are supplied, which is implicit in the schema default of 24 hours but not restated.

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 100%, so the schema already documents all four parameters, including the enum and the 1-168 hour bound. The description only adds asset examples (oil, grains, gas, semis, gold, Treasuries, country ETFs) that largely overlap the schema's own examples, so it adds little meaning beyond structured data.

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 names a specific resource (recent geopolitical, conflict and natural-hazard incidents) and a specific transformation (mapped to the asset classes and liquid proxies they are tagged against), with concrete examples of asset classes. It does not explicitly contrast itself with any sibling, but the sibling names (get_macro_regime, get_catalysts, get_earnings_reactions) are clearly distinct domains, so an agent can disambiguate.

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?

"Use this when you need recent geopolitical, conflict and natural-hazard incidents mapped to asset classes" gives a clear triggering condition and a scope of use. It does not state when NOT to use it or name an alternative tool, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources