Skip to main content
Glama

Zoom

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?

Beyond the readOnlyHint/openWorldHint/idempotentHint annotations, the description discloses meaningful runtime behavior: parallel fan-out across many sources, empty sections meaning real no-data rather than a bug, sources_used and sources_failed returning per-company status, GDELT-to-GNews fallback, and private companies returning resolved:false with an explicit notes line. No statement contradicts the 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 it is front-loaded with user-intent examples and the core value proposition before detailing sources and return fields. The source-by-source enumeration is information-dense and logically organized, though some of the example phrasings could be trimmed without losing meaning.

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 must explain return values, and it does so thoroughly: CIK, company_name, resolved_from/resolved_to, recent_filings with URIs, fundamentals, federal_contracts, fda_products, hiring, news, LEI, and sources_used/sources_failed. It also covers accepted inputs, private-company behavior, fallback logic, and the no-data-not-a-bug expectation, leaving little ambiguity for an agent.

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

Parameters4/5

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

The input schema already covers both parameters with 100% description coverage, so the baseline is 3. The description adds value by giving concrete accepted values (AAPL, 0000320193, Moderna), emphasizing zero-padded CIKs, explaining name resolution via SEC EDGAR, and clarifying that type=company and type=ticker behave interchangeably.

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 opens with concrete user queries and then states the core function: full cross-source profile of a US public company in ONE parallel call. This is a specific verb-resource-scope statement that clearly distinguishes the tool from single-source SEC/XBRL/news lookups.

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 this tool over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view, which is a clear when-to-use signal. It does not explicitly name sibling tools like compare_entities or resolve_entity or state when to choose those instead, so the exclusion guidance is incomplete.

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

All Zoom 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

The set mixes two entirely different domains: 4 Zoom tools and 31 Pipeworx/prediction-market tools. Within the Pipeworx side, ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions overlap heavily, as do the five polymarket_* tools. An agent could easily select the wrong variant despite the long descriptions.

Naming Consistency2/5

The Zoom tools follow a clean zoom_* pattern, and there are subfamilies like ask_pipeworx_* and polymarket_*, but the overall set is a mix of snake_case verbs, bare nouns, and inconsistent styles (bet_research, entity_profile, generate_llms_txt, list_subscriptions, pipeworx_feedback, validate_claim). No single predictable convention governs the server's tool names.

Tool Count2/5

35 tools is heavy for any server, and the vast majority are unrelated to the server's declared 'Zoom' purpose. Only 4 of 35 tools actually concern Zoom, making the count both bloated and mismatched. A focused Zoom server would need far fewer tools; a Pipeworx data server would need a different name.

Completeness2/5

For a Zoom server, the surface is critically incomplete: only read-only list/get operations exist for meetings, recordings, and the current user, with no create, update, delete, or invite functionality. The Pipeworx side is comparatively rich and complete, but that does not serve the Zoom domain implied by the server name, so significant gaps remain for the apparent purpose.

Resources