Skip to main content
Glama

Gtex

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. First observed

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, and non-destructive. The description adds valuable behavioral details: fan-out to multiple sources (SEC EDGAR, GDELT→GNews, USPTO), fallback logic, soft-fail for patents, and return structure (changes grouped by source, citation URIs). No contradictions.

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 front-loaded with example queries and clearly structured. It is slightly verbose (covers multiple sources in detail), but every sentence adds value for an agent. Could be marginally tighter but remains effective.

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?

Given high schema coverage, no output schema, and the tool's complexity (multiple sources, fallback logic), the description explains return structure (changes grouped by source, total_changes, citation URIs) and provides cross-reference to an alternative tool. No gaps.

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 coverage is 100% with descriptions for all three parameters. The description adds further meaningful context: type is only 'company', since accepts ISO dates or relative shorthand with examples, and value accepts ticker or CIK. This exceeds what schema alone provides.

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 companies over specified windows, with example queries and explicit differentiation from 'entity_profile' (static profile). It identifies the verb 'get recent changes' and the resource 'company change feed'.

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 gives explicit usage patterns ('What's new with X', 'latest on Y') and directly states when to use the alternative ('Use entity_profile instead when you want the static profile'). No ambiguity.

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

All Gtex 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

B3.3/5.0
Disambiguation2/5

ask_pipeworx and ask_pipeworx_beta are currently described as functionally identical, which is a direct ambiguity, and ai_visibility_check/scan_competitor_ai_presence plus the polymarket_* tools create several overlapping boundaries. The long descriptions help, but an agent still has to read deep into each one to avoid selecting the wrong tool.

Naming Consistency3/5

Most tools use readable lowercase snake_case verb_noun names like discover_tools, resolve_entity, and validate_claim, but the set also includes bare nouns like gene and tissues, verb-only memory tools like remember/recall/forget, and noun-phrase names like entity_profile, recent_changes, and pipeworx_trending. The style is not chaotic, but no single convention is sustained.

Tool Count2/5

36 tools exceeds the 25+ threshold and the surface is heavily padded with overlapping meta-tools, near-duplicate routers, and unrelated clusters such as Polymarket arbitrage, AI-visibility checks, and GTEx expression queries. For a server named Gtex, most of these tools are outside the apparent domain, making the count feel overgrown rather than well-scoped.

Completeness2/5

The GTEx-specific subset has only five tools and lacks obvious endpoints like multi-issue eQTLs, isoform expression, or sample-level querying, while the remaining 31 tools belong to unrelated Pipeworx, Polymarket, memory, and subscription domains. There is no coherent single purpose against which the surface can be considered complete, so agents will often hit dead ends or spend calls figuring out what the server is actually for.

Resources