Skip to main content
Glama

Dataverse Harvard

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

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavioral context: source fan-out, GDELT→GNews fallback, USPTO sunset soft-fail, expected absence of fda_products for small-molecule-only companies, empty sections meaning real 'no data', and the resolved:false behavior for private companies.

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 front-loaded with examples and the key directive, and it is dense but purposeful given the tool's wide scope and the absence of an output schema. It loses some readability by being one very long, loosely structured block rather than using paragraphs or bullets.

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?

Given the tool's complexity and lack of an output schema, the description is remarkably complete: it covers accepted inputs, all output sections, source fallbacks, known limitations, and expected edge-case behaviors. An agent has enough information to invoke it correctly and interpret results in most scenarios.

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

Parameters5/5

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

Schema coverage is 100%, establishing a baseline of 3, but the description enriches parameter semantics significantly: it states that type='company' and type='ticker' are interchangeable, details accepted value shapes (ticker, zero-padded CIK, company name), and explains name resolution via SEC EDGAR plus the private-company outcome.

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 operation—'full cross-source profile of a US public company in ONE parallel call'—with concrete example queries and a detailed list of data sources (SEC EDGAR, XBRL, patents, contracts, FDA, H-1B, news, GLEIF). This clearly distinguishes it from narrower lookup tools among the siblings.

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 gives an explicit routing rule: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also clarifies the private-company path (returns resolved:false with notes). It does not explicitly name sibling tools like resolve_entity or compare_entities as alternatives for narrower or comparative use cases.

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

All Dataverse Harvard 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

B3.4/5.0
Disambiguation3/5

Several tool pairs have overlapping purposes, notably ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded. Also, remember/recall/forget overlap with general memory operations, and multiple polymarket tools overlap in edge detection. While the descriptions attempt to differentiate, an agent will frequently need to choose between nearly identical tools (e.g., ask_pipeworx vs. ask_pipeworx_beta).

Naming Consistency2/5

Naming conventions are mixed: snake_case (ai_visibility_check, compare_entities), camelCase (ask_pipeworx, generate_llms_txt), and inconsistent verb usage (some start with verbs like 'search', others with nouns like 'dataset'). The polymarket and pipeworx prefixes are helpful, but overall patterns are unpredictable.

Tool Count2/5

With 35 tools, this server has a very large surface area. While the domain is broad (Harvard Dataverse + Pipeworx data + Polymarket), the count feels heavy and includes many near-duplicate tools (ask_pipeworx variants) and niche tools that inflate the total. Many agents would benefit from a smaller, more focused set.

Completeness3/5

The Dataverse subset captures file metadata and search but lacks direct download/upload capabilities, causing dead ends for users who want to access actual data. The Polymarket subset lacks the ability to actually place orders despite extensive edge analysis. The Pipeworx subset covers many data queries but feels unfocused. Overall, there are notable gaps given the stated scope of the server.

Resources