Skip to main content
Glama

Osv

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

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

With annotations already providing readOnly/openWorld/idempotent/destructive shadows, the description adds rich behavioral detail: it enumerates the exact sources fanned, clarifies that `sources_failed` means a real gap, explains that a private company returns resolved:false with a `notes` line, and flags expected empty FDA sections. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but the complexity of a cross-source fan-out tool justifies it. It is front-loaded with trigger examples and a one-line purpose, then structured into source list, return fields, input forms, and edge-case behavior. Every sentence carries operational value and there is no filler.

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 carries the full burden of explaining return shape, and it does so thoroughly: it lists the returned fields, source-specific quirks (e.g., patents soft-fail, FDA empty sections expected), resolution behavior, and failure semantics. An agent has enough to predict success and failure modes without further probing.

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%, but the description adds significant meaning beyond names: it explains that `value` accepts a ticker, zero-padded CIK, or company name interchangeably, that `type` values behave identically, and that names resolve via SEC EDGAR's company-name match. This goes well beyond the baseline 3.

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.' Trigger examples ('Tell me about X', 'research Acme') make intent unmistakable, and it explicitly distinguishes itself from chaining single-pack 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?

It gives an explicit usage rule: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' This clearly states when to use the tool over one class of alternatives, but it does not address overlapping siblings like resolve_entity or compare_entities, so it lacks explicit when-not guidance for those cases.

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

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

A4/5.0
Disambiguation3/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are very similar, as are the suite of polymarket_* tools. While descriptions help differentiate, an agent may struggle to choose the correct one without careful reading.

Naming Consistency3/5

All tool names use snake_case, but they mix verb-first patterns (ask_pipeworx, compare_entities, validate_claim) with noun-first patterns (bet_research, entity_profile, pipeworx_feedback). This inconsistency makes it harder to guess tool names by convention.

Tool Count3/5

35 tools is on the high side but not unreasonable for a platform covering vulnerability queries, data retrieval, prediction markets, and utilities. However, the server name 'Osv' suggests a narrow focus, making the large count feel bloated.

Completeness4/5

The tool set covers a wide range of operations: querying data, comparing entities, managing user data, monitoring subscriptions, and even onboarding. Minor gaps exist (e.g., no direct API for updating user profiles), but overall it is well-rounded for its domain.

Resources