Skip to main content
Glama

Securitytrails

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").

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive. Description adds details on GDELT→GNews fallback, USPTO soft-fail, and return structure (changes grouped by source, count, 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?

Description is a single dense paragraph with efficient use of examples and details. Slightly long but every sentence adds value.

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?

No output schema, but description explains return fields. Covers multi-source behavior, fallback, and soft-fail. Could mention handling of empty results.

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 has 100% coverage. Description adds examples for since (ISO date and relative shorthand, including recommendation), constrains type to 'company', and explains value as ticker or CIK.

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 provides a change feed for a company in a given time window, covering SEC, news, and patents. It distinguishes from sibling tool entity_profile by contrasting dynamic vs. static profiles.

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?

Provides explicit example queries (e.g., 'What's new with X') and contrasts with entity_profile for static profile requests. Explains fallback behavior for news sources.

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

All Securitytrails 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.8/5.0
Disambiguation2/5

Multiple tools occupy the same general query/research space: ask_pipeworx, ask_pipeworx_beta (currently identical), ask_pipeworx_grounded, deep_research, validate_claim, entity_profile, and recent_changes all overlap in what they can return. The descriptions are detailed and try to steer usage, but the boundaries are fuzzy enough that agents can easily select the wrong tool.

Naming Consistency3/5

All names are snake_case and descriptive, but there is no consistent verb_noun convention across the set. It mixes bare verbs (remember, recall, forget), noun phrases (entity_profile, recent_changes), domain-prefixed families (securitytrails_*, polymarket_*), and Pipeworx meta-tools (ask_pipeworx_*), so the pattern is predictable only within each family.

Tool Count2/5

35 tools is above the 25+ threshold for a coherent MCP surface, and many are highly specialized (Polymarket arbitrage, AI visibility checks, npm dependency scans) rather than core Securitytrails functionality. The set feels like multiple products merged into one rather than a well-scoped toolset.

Completeness3/5

The broad data-research workflows are well covered: routing, entity resolution, profiling, comparison, validation, subscriptions, memory, and basic Securitytrails domain lookups. But for a server named Securitytrails, there are obvious missing security-intelligence operations such as associated domains, IP/certificate enrichment, and broader DNS infrastructure enumeration.

Resources