Skip to main content
Glama
Sign In

OT Intel API

by io.github.No3men60
OverviewDiscussionsAdmin

CISA ICS-CERT Advisory Feed

getAdvisories
Read-only

CISA ICS advisories by vendor or sector from CISA's full CSAF history (since 2010), newest first. CVSS from the advisory, missing scores from NVD. Returns advisory IDs, CVE scores, vendors, CISA sectors, OT severity and triage links. One of vendor or sector is required. Price: $0.02 USDC per call via x402 on Base mainnet. An unpaid call returns an x402 PaymentRequired challenge; retry the identical call with the signed payload in _meta["x402/payment"].

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, default 10, max 25
modelNoYour device model (e.g. s7-1500): advisories naming it first, and asset_match per advisory
sinceNoOnly advisories first published on or after this date (YYYY-MM-DD)
sectorNoSector filter e.g. energy, water, manufacturing
vendorNoVendor filter e.g. siemens, schneider, rockwell
firmwareNoYour firmware version (e.g. 2.9.2), used with model: affected | related_product | not_affected | version_unknown | model_not_listed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / firmware
      Added value: +{
+  "description": "Your firmware version (e.g. 2.9.2), used with model: affected | related_product | not_affected | version_unknown | model_not_listed",
+  "type": "string"
+}
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Your device model (e.g. s7-1500): advisories naming it first, and asset_match per advisory",
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Page size, default 10"New value: +"Page size, default 10, max 25"
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +25
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Only advisories first published on or after this date (YYYY-MM-DD)",
+  "format": "date",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds everything else that matters: paid call at $0.02 USDC via x402 on Base mainnet, the exact failure mode (PaymentRequired challenge), and the retry mechanics (_meta["x402/payment"] with signed payload). It also discloses ordering, CVSS source with NVD fallback for missing scores, and the returned field set.

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?

Four front-loaded sentences, each carrying distinct information: scope, data-quality behavior, return contents, required-filter rule, and payment flow. The payment sentence is dense but necessary; nothing is padding.

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?

For a paid, open-world read tool with no output schema, the description covers scope, ordering, return shape, the required-filter constraint, and the complete payment/retry lifecycle. An agent has everything needed to call it and handle its failure mode.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds a constraint the schema does not express: vendor or sector must be supplied even though the schema lists zero required parameters. It does not explain the model/firmware interaction or the 'since' date semantics beyond the schema, keeping it from a 5.

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 a specific verb and resource — CISA ICS advisories — with scope (full CSAF history since 2010) and ordering (newest first). No sibling tool in the list covers an advisory feed, so it is unambiguous without needing differentiation.

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

Usage Guidelines3/5

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

The description gives a hard quirk rule — 'One of vendor or sector is required' — which is genuinely useful usage guidance. But it never says when to prefer this over adjacent tools (getDeviceExposure, getVendorRisk, getCveTriage) when an agent has a device or CVE in hand. Usage is implied, not routed.

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

All OT Intel API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources