Skip to main content
Glama

Data Rennes

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

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

Adds substantial behavior beyond the readOnly/openWorld/idempotent annotations: multi-source parallel fan-out with a GDELT→GNews fallback, USPTO soft-fail behavior ('soft-fails until reactivated'), expected-empty semantics ('a company with only small-molecule/generic drugs will show none here, that is expected, not a failure'), and the sources_used/sources_failed contract distinguishing real absence 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.

Conciseness3/5

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

Front-loaded with intent and every clause carries meaning, but the description is a single dense unbroken wall of text with deep nested parentheticals (e.g., the patents sunset aside and the fda_products explanation). It restates input-format information already fully covered by the schema, and would benefit from bulleted sections given its length.

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?

Despite having no output schema, the description enumerates all return sections (cik, company_name, recent_filings with URIs, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI, sources_used/sources_failed), all accepted input forms, and edge-case outcomes (private company, empty sections, soft-fails). An agent has everything needed to invoke it correctly for a complex multi-source tool.

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 coverage is 100% and the schema already documents that type accepts 'company' or 'ticker' interchangeably and that value takes a ticker, zero-padded CIK, or company name. The description reinforces this and adds the resolved_from/resolved_to and private-company resolved:false edge cases, which is helpful but does not substantially exceed what the schema already conveys.

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?

States a specific verb and resource: 'full cross-source profile of a US public company in ONE parallel call,' backed by example user phrasings. It distinguishes itself from alternatives by enumerating the exact sources it fans out across (SEC EDGAR, XBRL, USPTO, USAspending, Purple Book, DOL, GDELT/GNews, GLEIF) and explicitly says to prefer it over chained single-pack 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?

Gives an explicit preference rule: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' which is clear when-to-use guidance. It does not, however, name sibling tools like compare_entities or resolve_entity as alternatives, nor state explicit when-not-to-use conditions beyond the implicit private-company case.

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

All Data Rennes 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.1/5.0
Disambiguation3/5

Many tools have overlapping purposes, such as multiple data query tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) and several prediction market analysis tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.). While descriptions attempt to differentiate, an agent could easily select the wrong tool.

Naming Consistency3/5

Tool names use a mix of verb-initial (ask_pipeworx, compare_entities) and noun-phrase patterns (entity_profile, dataset_info), with no consistent verb_noun structure. Naming is readable but lacks a predictable pattern.

Tool Count3/5

With 34 tools, the server is on the heavy side. The broad scope (data querying, prediction markets, company research, local open data) somewhat justifies the count, but several tools could be consolidated (e.g., the various polymarket tools).

Completeness4/5

The tool set covers a wide range of functionalities including data querying, company research, prediction market analysis, and memory management. Minor gaps exist (e.g., no user authentication tools beyond subscriptions), but the surface is largely comprehensive for its intended purpose.

Resources