Skip to main content
Glama

Sciencebase

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.

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses far beyond the readOnly/idempotent annotations: fan-out sources, fallback behavior ('GDELT→GNews'), soft-fail for USPTO PatentsView, empty-section semantics ('a real no data, not a bug'), and the FDA expectation that small-molecule-only companies show no biologics. These are exactly the behavioral traits an agent needs.

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?

Front-loaded with trigger examples and the core promise of one parallel call. It is a dense single paragraph and repeats some schema information (type/value shapes), but the source-level caveats and edge-case explanations are functional, not 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 must explain return shape, and it does: CIK/company_name, recent_filings with URIs, fundamentals from latest 10-K, sources_used/sources_failed, and resolved:false for private companies. It is complete enough for an agent to call and interpret results correctly.

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 covers both parameters at 100%, so the baseline is 3. The description adds meaningful nuance: name resolution via SEC EDGAR, resolved:false notes for private companies, and resolved_from/resolved_to behavior when value is a name. Some type/value detail is redundant with the schema, which keeps it from a 5.

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 explicitly states it produces a full cross-source profile of a US public company, with concrete trigger phrases like 'Tell me about X' and 'company profile for Microsoft'. It also distances itself from single-pack lookups ('ALWAYS PREFER over chaining...'), so an agent can tell it apart from narrow SEC/XBRL/news tools.

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?

Gives a clear when-to-use rule: prefer this over chaining single-pack lookups whenever the user asks for a holistic view. It also specifies accepted input forms and the private-company edge case, but it never names sibling alternatives explicitly (e.g., resolve_entity for pure resolution), 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 Sciencebase 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 distinctly described purposes, but there is some overlap among query tools like ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim, which could cause confusion for an agent.

Naming Consistency3/5

Tool names are consistently snake_case but vary in pattern: some are verb_noun (ask_pipeworx, compare_entities), while others are noun_noun (entity_profile, polymarket_arbitrage) or longer phrases (scan_competitor_ai_presence), making the naming system inconsistent.

Tool Count2/5

With 33 tools, the server feels over-scoped. Many tools are niche (e.g., polymarket-specific ones) and the high number exceeds the typical range for a focused server, leading to potential overwhelm.

Completeness3/5

The server covers a broad range of query and monitoring tasks for its domains, but lacks write operations (except memory tools). There are notable gaps like no tool for creating or editing ScienceBase items, which seems incomplete given the server's name.

Resources