Skip to main content
Glama

Wikiquote

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds significant behavioral context: parallel fan-out to multiple sources, fallback logic, output structure (changes[] grouped by source, total_changes, citation URIs), and soft-fail for USPTO. No contradiction with annotations.

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 detailed but efficient, front-loading examples and purpose. Every sentence contributes meaningful information. Slightly verbose in parts (e.g., repeating fallback details) but still concise overall.

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?

Despite lacking an output schema, the description explains the return structure (changes[] grouped by source, total_changes, citation URIs). It covers input, behavior, output, fallbacks, and sibling distinction comprehensively. 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?

Input schema has 100% description coverage for 3 parameters. The description adds value: for 'since', it explains accepted formats and gives monitoring recommendation; for 'type', it notes only 'company' supported; for 'value', it clarifies ticker or CIK. This goes beyond schema 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's purpose: 'change feed for a company in the last N days/weeks/months in ONE parallel call.' It specifies the verb (provide change feed), resource (company), and scope (time window). It explicitly distinguishes from sibling tool entity_profile, stating when to use which.

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 provides explicit usage guidance: lists example queries ('What's new with X', 'latest on Y'), explains input formats (ISO date or relative shorthand), recommends '30d' or '1m' for typical monitoring, and directs users to entity_profile for static profiles. It also details fallback behavior for GDELT→GNews and USPTO soft-fail.

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

All Wikiquote 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/5.0
Disambiguation2/5

The tool set mixes four Wikiquote tools with 31 unrelated Pipeworx/Polymarket tools, creating a confusing dual identity. Within the research tooling, ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-synonyms, and polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk overlap heavily, making selection ambiguous.

Naming Consistency3/5

All names are snake_case, but patterns vary: some are verb-first (ask_pipeworx, compare_entities, resolve_entity), some noun-first (entity_profile, polymarket_arbitrage, quote_of_the_day), and several are bare verbs or nouns (search, summary, remember, quotes). Prefix groups like ask_pipeworx* and polymarket_* are consistent, but the overall convention is mixed.

Tool Count2/5

35 tools is excessive for a server named Wikiquote, as only 4 tools (quote_of_the_day, quotes, search, summary) actually serve that domain. The remaining 31 form an unrelated general research and prediction-market toolkit, making the set feel bloated and off-scope for its stated name.

Completeness1/5

As a Wikiquote server, the surface is severely incomplete: there is no random quote, page listing, author/topic browsing, or any write/update operations, and the few quotation tools are buried among unrelated functionality. The unrelated research tools may be internally rich, but they do not address the server's stated purpose.

Resources