Skip to main content
Glama

Poetrydb

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 nature. The description goes beyond by detailing the tool fans out to SEC EDGAR, GDELT/GNews (with fallback logic), and USPTO (soft-fail). It also outlines return structure (grouped changes, total count, citation URIs). 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 dense and front-loaded with query examples, then efficiently covers sources, fallbacks, and return format. A few sentences could be slightly more terse, but overall no wasted words.

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 the complexity of multiple sources (SEC, GDELT/GNews, USPTO) and lack of output schema, the description is remarkably complete. It covers input formats, source behavior, fallback logic, soft-fail for patents, and return structure (changes grouped by source, total count, citation URIs).

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. The description adds value by explaining the 'since' parameter accepts relative shorthand with examples (e.g., '30d', '3m'), noting that 'type' is constrained to 'company', and clarifying that 'value' can be a ticker or CIK. Provides guidance on typical usage ('30d' or '1m' for monitoring).

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 (SEC filings, news, patents) in a time window. It distinguishes from sibling 'entity_profile' by specifying that this tool is for dynamic updates, not 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?

Explicitly gives example queries ('What's new with X'), explains input formats (ISO date or relative shorthand), and advises when to use the sibling 'entity_profile' instead. Also describes fallback behavior between news sources.

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

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

Multiple tools have overlapping purposes, especially around Polymarket and Pipeworx (e.g., bet_research, polymarket_arbitrage, polymarket_edges, polymarket_kalshi_spread). Agents are likely to misselect among these similar tools.

Naming Consistency3/5

Naming conventions are mixed: some follow verb_noun (list_authors, search_poems), while others use more complex patterns (ai_visibility_check, scan_competitor_ai_presence). Still generally readable.

Tool Count2/5

30 tools is high but not extreme; however, the server name suggests a poetry database, yet only 4 of 30 tools relate to poetry. The scope is far too broad and mismatched, making the count inappropriate for the stated purpose.

Completeness2/5

For the poetry domain, only read/search operations are present, lacking any management tools. The other domains are covered by many tools but not cohesively integrated. The set has significant gaps relative to the server's stated name.

Resources