Equibles

Supply Chain

GetSupplyChain

Read-only

Get a company's supply chain: the customers, suppliers, competitors and partners named in annual 10-K reports, its own and those of other listed companies that name it, with any stated revenue or receivables share, a revenue share in dollars from the same filing, the verbatim sentence and the source filing. A share belongs to the filing that states it. Names the filings never state are not inferred, so a missing company is not evidence of no relationship. Requires the Pro plan.

Input Schema

Name	Required	Description	Default
`lens`	No	Order within each side: 'stated' (largest stated share first, the default), 'dependsOn' (largest share of this company's revenue first: who it relies on) or 'dependents' (largest share of the other company's own revenue first: who relies on it). A share is stated by a filing or derived from a stated share in dollars.	stated
`side`	No	Only one side: customers, suppliers, competitors or partners (default: all four).
`ticker`	Yes	Stock ticker symbol (e.g., AAPL, QRVO), or MIC:TICKER (e.g., XBRU:BAR) for a listing outside the US.
`maxResults`	No	Maximum companies listed per side (customers, suppliers, competitors, partners) (default: 50, max: 500). A company and the parts listed under it are kept together.
`quantifiedOnly`	No	Only companies with a stated revenue or receivables share (default: false).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedInput schema / properties / maxResults / description

Previous value: -"Maximum companies listed per side (customers, suppliers, competitors, partners) (default: 50, max: 500)."New value: +"Maximum companies listed per side (customers, suppliers, competitors, partners) (default: 50, max: 500). A company and the parts listed under it are kept together."

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / ticker / description

Previous value: -"Stock ticker symbol (e.g., AAPL, QRVO)."New value: +"Stock ticker symbol (e.g., AAPL, QRVO), or MIC:TICKER (e.g., XBRU:BAR) for a listing outside the US."

Changed4 schema fields changedOct 16, 2026

addedInput schema / properties / lens

Added value: +{
+  "default": "stated",
+  "description": "Order within each side: 'stated' (largest stated share first, the default), 'dependsOn' (largest share of this company's revenue first: who it relies on) or 'dependents' (largest share of the other company's own revenue first: who relies on it). A share is stated by a filing or derived from a stated share in dollars.",
+  "type": "string"
+}

changedInput schema / properties / maxResults / description

Previous value: -"Maximum companies listed per side (customers, suppliers, competitors, partners), stated shares first (default: 50, max: 500)."New value: +"Maximum companies listed per side (customers, suppliers, competitors, partners) (default: 50, max: 500)."

addedInput schema / properties / quantifiedOnly

Added value: +{
+  "default": false,
+  "description": "Only companies with a stated revenue or receivables share (default: false).",
+  "type": "boolean"
+}

addedInput schema / properties / side

Added value: +{
+  "default": null,
+  "description": "Only one side: customers, suppliers, competitors or partners (default: all four).",
+  "type": "string"
+}

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / maxResults / description

Previous value: -"Maximum companies listed per side (customers, suppliers, competitors), stated shares first (default: 50, max: 500)."New value: +"Maximum companies listed per side (customers, suppliers, competitors, partners), stated shares first (default: 50, max: 500)."

AddedOct 16, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, non-open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a plan/auth requirement, a provenance rule ('A share belongs to the filing that states it'), and a critical completeness caveat that absent names are not inferred and missing data is not evidence of no relationship.

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?

Purpose is front-loaded and every sentence carries content (scope, provenance, caveat, prerequisite). Sentences are long and clause-heavy, but nothing is padding 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?

With no output schema, the description must describe returns, and it does so concretely: the stated revenue/receivables share, a dollar revenue share from the same filing, the verbatim sentence, and the source filing. An agent has enough to call it and interpret results 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 lens, side, ticker, maxResults and quantifiedOnly are already documented in the schema; baseline is 3. The description's mention of 'stated revenue or receivables share' loosely relates to quantifiedOnly but adds no syntax or format detail beyond the schema.

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?

Specific verb (Get) and resource (supply chain), with the exact entity types returned (customers, suppliers, competitors, partners) and the bidirectional scope (its own 10-K and those of companies that name it). An agent can distinguish this from GetCustomerConcentration and GetSupplyChainOverlap without opening the schema.

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

Usage Guidelines3/5

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

States the plan prerequisite ('Requires the Pro plan') and the data source (annual 10-K filings), which frames when it applies, but never names an alternative sibling or a when-not condition. Usage is implied by the domain rather than explicitly routed.

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

All Equibles tools Inspect

Try in Browser