Skip to main content
Glama

ureweries

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

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare this read-only, idempotent, and non-destructive, so the description's job is to add behavioral context beyond that. It does so extensively: fan-out across SEC, XBRL, USPTO, USAspending, FDA, DOL, news, and GLEIF; patents soft-fail after the USPTO sunset; empty fda_products is expected for small-molecule-only companies; and sources_used/sources_failed distinguish genuine no-data 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 nearly every clause earns its place given the tool's complexity and the absence of an output schema. It front-loads the intent and use guidance, then packs the response-shape and edge-case behavior into a dense but organized list. The single very long sentence listing return fields is a minor readability cost.

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 complex tool with no output schema, the description covers the response shape (CIK, filings with URIs, fundamentals, patents, contracts, FDA products, hiring, news, LEI), the semantics of empty sections, failure modes (patents sunset, private company), and input flexibility. An agent has enough context to invoke it correctly and interpret results even without seeing real output.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics: the two 'type' values are interchangeable, 'value' can be a ticker, zero-padded CIK, or company name, and a private company without a CIK/ticker yields resolved:false with a notes field. This goes beyond the schema without being redundant.

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 phrasings ('Tell me about X', 'research Acme', 'brief me on Tesla') and states the exact function: a full cross-source profile of a US public company in one parallel call. It clearly differentiates itself from chaining single-source lookups, and its 'ALWAYS PREFER' guidance removes ambiguity about which sibling to choose for holistic research.

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?

It explicitly says when to use the tool — whenever a user asks for a holistic view of a company — and explicitly says to prefer it over chaining single-pack SEC/XBRL/news lookups. It also handles edge-case routing: names resolve via EDGAR, and private companies return resolved:false with a notes line rather than a bare failure.

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

All ureweries 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.9/5.0
Disambiguation4/5

Most tools have clear distinct purposes, but ask_pipeworx, ask_pipeworx_grounded, and deep_research overlap in querying Pipeworx data sources. Entity_profile and recent_changes also share some coverage. Overall, agents can differentiate, but a few pairs may cause confusion.

Naming Consistency3/5

Tool names use snake_case for multi-word (e.g., ai_visibility_check) but also single-word verbs (forget, recall, remember). The pattern is not uniform: some are verb_noun, some are just noun or verb. Mixed conventions reduce predictability.

Tool Count3/5

At 33 tools, the set is on the high side for an MCP server. The server covers a broad data-query domain, which justifies many specialized tools, but the count is borderline heavy and includes several meta-tools (discover_tools, suggest_questions). Could be streamlined without losing core functionality.

Completeness4/5

The tool surface is comprehensive for data retrieval across financial, economic, pharmaceutical, real estate, weather, and prediction markets. It includes both single-lookup and comparative tools, plus monitoring via subscriptions. Minor gaps exist (e.g., no direct update/delete for user memory beyond forget), but the core domain is well-covered.

Resources