Skip to main content
Glama

advice

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

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses several important behavioral traits: it fans out across many sources, soft-fails for the USPTO PatentsView sunset, treats empty sections as real 'no data' rather than errors, resolves names via SEC EDGAR, returns resolved:false for private companies with a notes line, and uses a GDELT→GNews fallback. This gives the agent a strong model of what happens at runtime.

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 dense and front-loaded with query examples and the all-important usage preference. Every major clause contributes either a source, a return field, or a failure-behavior note, so the length is justified. It could be slightly trimmed, but structure, backticked literals, and semicolon-separated sections keep it scannable.

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 there is no output schema, the description carries the full burden of describing return data, and it does so thoroughly: cik, resolved_from/resolved_to, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI, plus sources_used/sources_failed. It also covers input resolution, failure modes, and expected empty results, so an agent has enough context to invoke it and interpret its output correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already fully documents 'type' and 'value' including examples and the interchangeability of both type values. The description adds natural-language examples and emphasizes the zero-padded CIK form and name resolution, but it mostly repeats schema semantics rather than introducing genuinely new parameter meaning. Baseline 3 applies.

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 uses concrete verbs and examples like 'Tell me about X' / 'research Acme' and defines the resource as a 'full cross-source profile of a US public company.' It clearly differentiates the tool's scope from single-pack SEC/XBRL/news lookups, and the sibling set (compare_entities, resolve_entity, deep_research) is implicitly distinguished by this holistic-company-profile framing.

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 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' which is strong when-to-use guidance. It also notes behavior for private companies and that type accepts either 'company' or 'ticker,' but it does not explicitly contrast this tool with siblings like deep_research or compare_entities, so the routing guidance is slightly incomplete.

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

All advice 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.7/5.0
Disambiguation2/5

The ask_pipeworx family is a major confusion source: ask_pipeworx_beta explicitly states it 'currently matches ask_pipeworx exactly', and ask_pipeworx_grounded/deep_research heavily overlap with the base router. polymarket_edges vs polymarket_arbitrage and discover_tools vs suggest_questions also have fuzzy boundaries, though long descriptions partially mitigate the overlap.

Naming Consistency4/5

All tool names are lowercase snake_case, and most follow a verb_noun pattern (validate_claim, resolve_entity, compare_entities, generate_llms_txt). A few bare verbs (remember, recall, forget) and noun-style names (entity_profile, polymarket_arbitrage, pipeworx_trending) deviate slightly, but the overall style is predictable and readable.

Tool Count2/5

34 tools is heavy and spans several unrelated domains: Pipeworx data research, prediction markets, subscriptions, memory, AI visibility, advice slips, npm dependency checks, and llms.txt generation. The count is inflated by near-duplicate research routers and disconnected outliers like generate_llms_txt and scan_dependency, making the set feel like a kitchen sink rather than a focused server.

Completeness3/5

The Pipeworx research and prediction-market surfaces are quite complete (ask, grounded, deep research, entity profile, compare, resolve, validate, subscriptions with full lifecycle, memory with save/recall/delete). However, the server is named 'advice' yet the advice domain only has three thin tools (get/search/random) with no other operations, and the mixed domains leave obvious dead ends for any single stated purpose.

Resources