Skip to main content
Glama

swapi

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?

Beyond the readOnly/idempotent annotations, the description discloses multi-source fan-out (SEC, GDELT/GNews, USPTO), the GDELT-priority fallback logic, the USPTO sunset soft-fail, and the return structure (changes[] grouped by source, total_changes, citation URIs). This is rich, non-redundant behavioral context.

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 dense but well-organized, front-loading examples and then covering multi-source behavior, parameters, and alternatives. Every sentence contributes useful information, though it could be slightly trimmed; it earns a 4 rather than 5.

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 is complex (multi-source aggregation, fallbacks, time handling), and the description covers all key aspects: input formats, source behavior, fallback conditions, output structure, and an explicit alternative. Without an output schema, the description still fully informs the agent about return values and edge cases.

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 baseline is 3. The description adds practical value by explaining `since` accepts ISO dates or relative shorthand, recommending '30d'/'1m' for monitoring, and clarifying that `value` can be a ticker or CIK—details beyond the schema's own descriptions.

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 time-windowed change feed for a company, backed by concrete example queries ('What's new with X', etc.). It distinguishes itself from the sibling entity_profile by explicitly noting that tool for static profiles, making the purpose and scope unmistakable.

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 scenarios with example queries, specifies fallback behavior (GDELT→GNews) and soft-fail conditions, and directly names entity_profile as the alternative for static profiles. This tells the agent exactly when to use this tool versus the sibling.

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

All swapi 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.7/5.0
Disambiguation3/5

The tool set mixes two unrelated domains (Star Wars and Pipeworx data services), which is initially confusing. Within the Pipeworx suite, tools like ask_pipeworx and ask_pipeworx_grounded are clearly differentiated, but some overlap exists (e.g., deep_research vs. compare_entities both do multi-source lookups). Overall, most tools have distinct purposes, but the domain mismatch lowers clarity.

Naming Consistency4/5

All tools use snake_case consistently (e.g., ask_pipeworx, entity_profile, resolve_entity). The naming pattern is mostly verb_noun or descriptive_compound, which is predictable. Minor deviation: some tools start with a verb (ask_pipeworx) while others start with a noun (entity_profile), but the style is uniform.

Tool Count3/5

34 tools is on the high side but not unreasonable for a data-heavy server. However, the set covers two distinct domains (Star Wars and Pipeworx), making it feel bloated. The count could be reduced by separating the domains or pruning rarely-used tools.

Completeness3/5

The Pipeworx side appears comprehensive, covering queries, profiles, comparisons, subscriptions, alerts, and memory. The Star Wars side is incomplete—it lacks tools for vehicles, species, or individual characters (only search_people exists). The overall surface has gaps in one of its two domains.

Resources