Skip to main content
Glama

Isbn

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.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds rich behavioral context: fans out to multiple sources, fallback logic, soft-fail, and return format (changes[] grouped by source, total_changes, 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 fairly long but well-structured with examples, fallback explanation, and alternative tool mention. Every sentence adds value, but slightly verbose.

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?

No output schema exists, but the description compensates by detailing the return structure. It covers purpose, usage, parameters, sources, and alternatives, making it complete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions for each parameter, including example values. The description reinforces but does not add significant new meaning beyond the schema. Baseline 3 is appropriate.

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 provides specific example queries and states it's a change feed for a company in a recent time window. It details the sources (SEC EDGAR, GDELT→GNews, USPTO) and explicitly distinguishes from the sibling tool 'entity_profile'.

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 explains when to use this tool (e.g., 'what's new with X') and when not to use it ('Use entity_profile instead...'). It also covers fallback behavior between GDELT and GNews and soft-fail for USPTO.

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

All Isbn 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
Disambiguation4/5

Most tools have clearly distinct purposes (entity_profile, compare_entities, ask_pipeworx, etc.). However, ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are very similar, and suggest_questions/discover_tools overlap slightly. Overall, tools are well-disambiguated with only minor ambiguity.

Naming Consistency3/5

All tool names use snake_case, but the pattern is inconsistent: some start with a verb (ask_, validate_), others with a noun (entity_, bet_). Several are noun_noun (entity_profile), and some are single verbs (remember). No consistent verb_noun pattern across the set.

Tool Count2/5

33 tools is excessive for a server named 'Isbn' that only has 2 ISBN-specific tools. The majority are from Pipeworx, creating scope mismatch. Multiple redundant tools (three ask_pipeworx variants, several polymarket tools) inflate the count unnecessarily.

Completeness2/5

For a server named 'Isbn', completeness is very low—only conversion and validation are provided; no metadata lookup or other ISBN-related features exist. The Pipeworx tools themselves are comprehensive, but they do not align with the server's implied domain.

Resources