Skip to main content
Glama

Roblox

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

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

The description adds extensive behavioral context beyond the readOnly/openWorld/idempotent annotations: it fans out across multiple upstream sources, returns sources_used/sources_failed, soft-fails on the USPTO PatentsView sunset, shows empty FDA sections for companies without biologics, and explicitly states that an empty section is real 'no data.' It also discloses the return structure for each section, including sorting and fallback behavior for news. All of this is consistent with the annotations, so there is no contradiction.

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 every sentence earns its place for a tool with no output schema and a complex multi-source return contract. It is front-loaded with purpose and usage guidance before diving into the source/field breakdown, and it is internally organized by semicolons and return-field names. It loses a point only for being a dense wall of text that could benefit from more visual structure, but there is no fluff or repetition.

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 that there is no output schema, the description carries the full burden of explaining return values and behavior. It covers every major output section (cik/company_name, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI), each source's semantics, the sources_used/sources_failed signals, input resolution rules, and edge cases such as private companies and empty FDA sections. Nothing an agent would need to call the tool correctly and interpret its response is missing.

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%: both the `type` and `value` parameters already have detailed descriptions covering the accepted shapes ('ticker, CIK, or company name') and the interchangeability of 'company' vs 'ticker'. The description mostly restates this ('type accepts company or ticker interchangeably') and adds only a small extra note that names resolve via SEC EDGAR's company-name match. Baseline 3 is appropriate because the schema carries the heavy lifting and the description adds marginal value.

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 opens with concrete usage examples ('Tell me about X', 'research Acme', 'brief me on Tesla') and then states a specific verb-resource pair: 'full cross-source profile of a US public company in ONE parallel call.' It also differentiates itself from sibling-style alternatives by explicitly saying 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups.' This leaves an agent with no doubt what the tool accomplishes and how it differs from nearby tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when to use this tool: when the user asks for a holistic view of a company, and explicitly tells it to be preferred over chaining single-source lookups. It also covers input variations (ticker, CIK, name) and the private-company edge case with 'resolved:false' and a notes line instead of a bare failure. This is far beyond the minimum viable guidance and provides clear when/when-not context.

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

All Roblox 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.1/5.0
Disambiguation4/5

Most tools have distinct purposes, especially within the Roblox and Pipeworx domains. However, the three variants of ask_pipeworx (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are very similar and could cause confusion, as could deep_research vs ask_pipeworx.

Naming Consistency3/5

Naming conventions are mixed: snake_case (user_followers_count), verb_noun with underscores (ask_pipeworx), and camelCase (recall, forget). Roblox tools follow a consistent 'user_' prefix, but Pipeworx tools lack a uniform pattern.

Tool Count2/5

41 tools is excessive for a server named 'Roblox'. The majority of tools are Pipeworx data utilities, which are unrelated to the server's apparent focus. This overloading undermines coherence.

Completeness3/5

Coverage within the Roblox domain is basic (user profiles, friends, games) but misses common features like asset details or group management. Pipeworx appears comprehensive for data lookups, but the overall set lacks unified domain completeness.

Resources