Skip to main content
Glama

Theaudiodb

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

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

Beyond the annotations, the description discloses the cross-source fan-out, the `sources_used`/`sources_failed` fields, the meaning of empty sections, name resolution via SEC EDGAR, and the private-company `resolved:false` behavior. These details help an agent interpret results and avoid treating missing data as a failure. The behavior is fully compatible with readOnlyHint and idempotentHint.

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 and dense, but it is front-loaded with purpose and usage preference, then organized into sources, returns, and input shapes. The many utterance examples are useful for intent matching. A garbled fragment like "sorted?" and some run-on enumeration keep it from being perfectly clean.

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?

Since there is no output schema, the description carries the burden of explaining the response, and it does so by enumerating the return sections and the `sources_used`/`sources_failed` flags. It also covers edge cases: name resolution, private companies, and empty sections meaning real absence of data. For a broad read-only profile tool, this is complete enough for an agent to call it correctly.

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 covers both parameters completely, including the interchangeability of `type` values and the accepted `value` forms. The description mostly restates the same examples and rules rather than adding new parameter-level meaning. The private-company note is useful but is more of an output/response guarantee than a semantic extension of the parameters.

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 states a specific verb and resource: it produces a "full cross-source profile of a US public company in ONE parallel call" and backs it with concrete query examples. This clearly distinguishes the tool from chaining single-pack SEC/XBRL/news lookups and from general search tools. It is not a tautology and tells an agent exactly what entity_profile does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to "ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view," which is a practical decision rule. It does not spell out exclusions for sibling tools like deep_research or compare_entities, but the holistic-view trigger gives clear enough context for typical use. There is no misleading guidance.

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

All Theaudiodb 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
Disambiguation3/5

Most tools have clearly distinct purposes and detailed descriptions, but ask_pipeworx and ask_pipeworx_beta are currently identical, and several data-answer/prediction-market tools overlap in intent. The music tools are generally separable once name-vs-ID and album-vs-track distinctions are recognized.

Naming Consistency4/5

The vast majority of tools follow lowercase snake_case with a verb-first or domain-prefixed pattern (search_artist, get_album_tracks, validate_claim, polymarket_edges). Minor deviations like remember/recall/forget and recent_alerts/recent_changes break the pattern slightly but do not create real confusion.

Tool Count1/5

35 tools is far too many for a server named TheAudioDB, and only 4 of them are actually music-metadata tools. The remaining 31 tools form an unrelated Pipeworx/Polymarket data-research platform, which is an extreme scope mismatch rather than a modest overage.

Completeness2/5

The music-metadata surface covers artist search, album search, artist-by-ID, and album tracks, but there is no track search, no album-by-ID getter, and no general track lookup, so common music queries will dead-end. The unrelated Pipeworx side is broad, but for a server presented as TheAudioDB the domain coverage has significant gaps.

Resources