Skip to main content
Glama

particle-pro

by pro.particle
OverviewDiscussionsAdmin

Particle Company Get

particle_company_get
Read-only

Return a bundled profile for one company: identifiers (slug, ticker, domain, CIK, QID, linked entity), name, and description.

Request optional sections via include: 'people' for current leadership and notable people (person slugs feed particle_person_get), 'products' for the three-level product hierarchy, 'competitors' for the competitor list, 'external_links' for the company's LinkedIn, social profiles, domain, Wikidata QID, SEC CIK and tickers. The default response is lean — include only what you need.

For sponsor/advertising analytics on this company, use particle_company_get_podcast_ad_presence instead.

Input Schema

NameRequiredDescriptionDefault
includeNoOptional response sections: 'people' (current leadership and notable people), 'products' (three-level product hierarchy), 'competitors' (competitor list), 'podcast_recommendations' (the ten podcasts the company could advertise on next, with the shows it already buys that led there; premium), 'external_links' (LinkedIn, social profiles, domain, Wikidata QID, SEC CIK and tickers). Default response is lean — request only what you need.
company_slugYesCompany identifier — accepts slug (e.g. 'nvidia'), domain (e.g. 'nvidia.com'), or canonical ID. If you already know the domain you can call this tool directly without first running particle_company_resolve.
product_statusNoComma-separated lifecycle filter for include=products (e.g. 'active' or 'active,announced'). Allowed values: active, announced, discontinued, rumored. Defaults to 'active'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / include / description
      Previous value: -"Optional response sections: 'people' (current leadership and notable people), 'products' (three-level product hierarchy), 'competitors' (competitor list), 'podcast_recommendations' (the ten podcasts the company could advertise on next, with the shows it already buys that led there; premium). Default response is lean — request only what you need."New value: +"Optional response sections: 'people' (current leadership and notable people), 'products' (three-level product hierarchy), 'competitors' (competitor list), 'podcast_recommendations' (the ten podcasts the company could advertise on next, with the shows it already buys that led there; premium), 'external_links' (LinkedIn, social profiles, domain, Wikidata QID, SEC CIK and tickers). Default response is lean — request only what you need."
    • changedInput schema / properties / include / items / enum
      Previous value: -[
-  "people",
-  "products",
-  "competitors",
-  "podcast_recommendations"
-]New value: +[
+  "people",
+  "products",
+  "competitors",
+  "podcast_recommendations",
+  "external_links"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, non-destructive, open-world), and the description adds useful context: the default response is lean and sections are opt-in, with a note that person slugs feed particle_person_get. Doesn't discuss rate limits, auth, or premium gating beyond the schema, so slightly short of 5.

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?

Two tight paragraphs, front-loaded with the default response shape, then the include options, then routing to the alternative. Slightly dense but every sentence carries weight.

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?

For a read-only profile fetch with full schema coverage and no output schema, the description fully explains what returns by default, how to expand it, and where to go for adjacent data. Nothing an agent needs to call it correctly is missing.

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 coverage is already 100%, so baseline is 3; the description elevates by explaining the relationships between parameters — that `include` sections chain into particle_person_get and that `product_status` filters include=products. Minor gap: doesn't restate the product_status lifecycle values, but the schema does.

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 (Return) and resource (bundled profile for one company), enumerating exactly what fields come back (slug, ticker, domain, CIK, QID, name, description). Explicitly distinguishes itself from particle_company_get_podcast_ad_presence for ad analytics.

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?

Gives explicit when-to-use-the-alternative guidance ('For sponsor/advertising analytics... use particle_company_get_podcast_ad_presence instead'), notes it can be called directly with a domain without first running particle_company_resolve, and advises 'request only what you need.'

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

All particle-pro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources