Skip to main content
Glama

Alienvault Otx

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds behavioral details: fan-out to multiple sources, fallback behavior, soft-fail for USPTO, and output structure (changes[] grouped by source, total_changes, citation URIs). No contradiction.

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 description is a single paragraph but front-loaded with examples, then logically covers sources, parameters, and output. Some whitespace or structure could improve readability, but it's concise and informative.

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?

The tool has 3 parameters, no output schema. The description explains the output format and behavior thoroughly, including fallback and limitations. For a read-only tool, this is highly complete.

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

Parameters5/5

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

Schema description coverage is 100%. The description enriches parameter meaning: for since, explains ISO date vs relative shorthand and recommends '30d'/'1m'; for value, specifies ticker or CIK; for type, clarifies only 'company' is supported.

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 clearly states the tool returns a combined change feed (SEC filings, news, patents) for a company in a time window. It distinguishes from sibling tool entity_profile and provides example queries for context.

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

Usage Guidelines5/5

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

The description explicitly gives usage patterns ('What's new with X', 'latest on Y') and contrasts with entity_profile for static profiles. It explains fallback logic (GDELT→GNews) and advises on typical since values ('30d' or '1m').

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

All Alienvault Otx 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

A3.6/5.0
Disambiguation1/5

Several tools are nearly indistinguishable, particularly ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded, plus a cluster of overlapping Polymarket tools. The three OTX-specific tools are buried among 31 unrelated utilities, making correct selection highly error-prone.

Naming Consistency3/5

Tool names are consistently snake_case and mostly readable, but the pattern is mixed: imperative verbs like ask_, get_, lookup_, and validate_ coexist with noun-first names like entity_profile, polymarket_edges, and recent_alerts. It is not chaotic, but the style is not predictable enough for a 5.

Tool Count2/5

34 tools is excessive for a server purportedly about Alienvault OTX, with only 3 tools actually serving that domain. The bulk are unrelated data-retrieval, prediction-market, memory, and utility tools, making the set feel unfocused and overstuffed.

Completeness1/5

For a server named Alienvault OTX, the surface is severely incomplete: search_pulses, get_pulse, and lookup_indicator cover only basic threat-intel lookup. There is no coverage of OTX events, malware details, passive DNS, indicator enrichment, or OTX subscription workflows, while most of the 34 tools address entirely different domains.

Resources