Skip to main content
Glama

Openiban

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when value was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. sources_used / sources_failed say which of these actually returned data for THIS company — an empty section is a real "no data", not a bug. Pass a ticker ("AAPL"), zero-padded CIK ("0000320193"), OR a company name ("Moderna") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit notes line, not a bare failure. type accepts "company" or "ticker" interchangeably — both take the same value shapes above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna") — names resolve via SEC EDGAR company-name match.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
    • changedInput schema / properties / value / description
      Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already carry readOnlyHint/openWorldHint/idempotentHint/destructiveHint, and the description adds substantial context beyond them: the USPTO PatentsView API sunset with soft-fail behavior, fda_products being legitimately empty for small-molecule-only companies ('expected, not a failure'), and `sources_used`/`sources_failed` semantics distinguishing real-empty from bugs. 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 long, but the tool fans out across ~10 data sources and has no output schema, so the density is largely earned. It is front-loaded with purpose and example queries before diving into source details. Could be tightened slightly, but every sentence carries real information.

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?

With no output schema, the description fully carries the return-shape burden — and it delivers: covers all returned sections (cik, recent_filings with URIs, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI), explains source fallbacks (GDELT→GNews) and error semantics. Nothing an agent needs to call it correctly is missing.

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% — both `type` and `value` are fully documented in the schema itself, so the baseline is 3. The description adds marginal value: clarifying the interchangeability of type values and that names resolve via SEC EDGAR company-name match, plus a 'person/place coming soon' hint. Helpful but not a major lift beyond the schema.

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?

States a specific verb+resource: 'full cross-source profile of a US public company in ONE parallel call.' Provides numerous concrete example utterances and explicitly differentiates from chaining single-pack SEC/XBRL/news lookups. No ambiguity about what this tool does.

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?

Explicit when-to-use guidance: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' Addresses the alternative approach directly and describes boundary conditions (private companies return resolved:false with notes). Agent is never left guessing.

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

All Openiban 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 heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and the polymarket_* family (edges, arbitrage, edge_tracker, fill_risk) blurs together for an agent trying to pick one. entity_profile and recent_changes also both pull company data, and ai_visibility_check vs scan_competitor_ai_presence are single-vs-multi variants of the same probe.

Naming Consistency3/5

Naming is mostly snake_case and readable, with many verb_noun forms (validate_iban, generate_llms_txt, resolve_entity). However, there are bare verbs (remember, forget, recall, subscribe, unsubscribe), noun phrases (entity_profile, recent_changes, pipeworx_trending), and inconsistent prefixes (ask_ vs polymarket_ vs suggest_) that break a clear pattern.

Tool Count3/5

33 tools is borderline-heavy for a data-research API, but the bigger issue is that the server is named Openiban yet contains only two IBAN tools and 31 unrelated Pipeworx/data tools. The count feels bloated and misaligned with the server's apparent identity, though not extreme enough for a 1 or 2.

Completeness2/5

For the Pipeworx data-research domain the surface is quite rich (query, deep research, entity profiles, comparisons, subscriptions, memory). For the server's stated IBAN purpose, only validate and suggest_iban exist — no generation, parsing, batch checks, or bank detail coverage — so the tool set is severely incomplete relative to the server name.

Resources