Skip to main content
Glama

exchangerate

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. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description reveals internal fallback behavior (GDELT preferred, GNews when rate-limited or 5xx), the soft-fail of USPTO due to API sunset, and the output structure (changes[] grouped by source, total_changes, citation URIs). This gives the agent a realistic model of the tool's behavior and limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than simple tools but every sentence is purposeful: the opening examples clarify intent, the fan-out explanation is dense but readable, and the alternative-tool guidance is valuable. It is front-loaded with natural language examples and structured logically.

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?

For a tool with multiple data sources and fallback logic, this description is remarkably complete. It covers the core behavior, output shape, source limitations, and even suggests parameter values. The annotations provide safety context, and the description fills in the behavioral details, so an agent can invoke the tool correctly without additional information.

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?

The input schema already provides comprehensive descriptions for all three parameters (100% coverage), including examples for `since` and formats for `value`. The description reiterates the `since` examples but does not add new semantic meaning beyond what the schema offers, so the baseline score of 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 clearly defines a 'change feed for a company' with concrete examples of user intents, and lists the exact data sources (SEC EDGAR, GDELT/GNews, USPTO). It also explicitly distinguishes itself from entity_profile, a sibling tool, by contrasting dynamic changes vs. 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?

The description provides explicit usage guidance: 'Use entity_profile instead when you want the static profile ... regardless of window.' It also recommends a specific value for `since` ('30d' or '1m' for typical monitoring), which helps the agent choose parameters appropriately.

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

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

Multiple tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates, while deep_research, validate_claim, and bet_research blur the same routing/grounding line. The polymarket_* family also has five tools covering edges, arbitrage, fill risk, and edge decay with significant functional overlap, making misselection likely despite very detailed descriptions.

Naming Consistency2/5

Naming mixes verb_noun tools (get_pair, compare_entities, suggest_questions) with noun-style tools (entity_profile, recent_changes, bet_research) and bare verbs (remember, recall, forget). The polymarket_ and pipeworx_ prefixes add some structure, but overall the naming is inconsistent and doesn't follow a predictable pattern.

Tool Count1/5

The server is named 'exchangerate' but exposes 33 tools, only two of which (get_pair, get_rates) relate to exchange rates. Even as a general data platform 33 tools is at the extreme high end, and for the stated server purpose the count is wildly inappropriate.

Completeness1/5

For an exchange-rate server, the surface is severely incomplete: there is no historical rate lookup, no amount conversion, no supported-currency listing, and no rate-change monitoring. The actual tool content covers a broad research platform, but that is entirely mismatched with the server name, leaving the implied exchange-rate domain almost completely uncovered.

Resources