Skip to main content
Glama

Scrutica

by io.github.davidgringras
OverviewDiscussionsAdmin

scrutica_get_supply_chain

Read-only

Return supply-chain relationships for one or more organizations. direction = 'upstream' traces suppliers (who feeds this entity); 'downstream' traces customers (who depends on this entity); 'both' returns both. Each edge carries supplier_org_id, customer_org_id and data_source; product_service, category, sole-source status, share and criticality appear only where the edge's cited source states them for that pair, and attribute_withholding gives the reason for every withheld value. Collection size: 20,798 supply-chain records across all sources (snapshot 2026-10-03). Of these records, 1,924 come from a licensed layer limited to relationships between organizations already in Scrutica's records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
org_idNoAlias for org_ids; a single id may be passed as a bare string.
org_idsNoREQUIRED. Scrutica org IDs in 'org-<slug>' format (e.g. ['org-nvidia', 'org-tsmc']), 1-5 of them. Optional in the schema only so the single-id aliases below can stand in.
directionNoboth
company_idNoAlias for org_ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / company_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ],
+  "description": "Alias for org_ids."
+}
    • addedInput schema / properties / org_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ],
+  "description": "Alias for org_ids; a single id may be passed as a bare string."
+}
    • changedInput schema / properties / org_ids / description
      Previous value: -"Scrutica org IDs in 'org-<slug>' format (e.g. ['org-nvidia', 'org-tsmc'])"New value: +"REQUIRED. Scrutica org IDs in 'org-<slug>' format (e.g. ['org-nvidia', 'org-tsmc']), 1-5 of them. Optional in the schema only so the single-id aliases below can stand in."
    • removedInput schema / required
      Removed value: -[
-  "org_ids"
-]
  2. Changed1 schema field changed
    • changedInput schema / properties / org_ids / description
      Previous value: -"Scrutica org IDs (e.g. ['nvidia', 'tsmc'])"New value: +"Scrutica org IDs in 'org-<slug>' format (e.g. ['org-nvidia', 'org-tsmc'])"
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish a safe read (readOnlyHint=true), so the description's added value is the return-shape caveats: optional fields 'appear only where the edge's cited source states them' and attribute_withholding explains withheld values. The licensed-layer coverage note (1,924 of 20,798 records restricted to already-known orgs) is genuinely useful behavioral context beyond the 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?

Purpose and direction semantics are appropriately front-loaded, but the final collection-size sentence (20,798 records, snapshot date, 1,924 licensed records) is informational rather than actionable for selecting or invoking the tool, so it does not fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 carries the return-value burden and does so reasonably, naming the always-present edge fields (supplier_org_id, customer_org_id, data_source) and the conditionally present attributes plus attribute_withholding. Remaining minor gaps are the alias parameters and pagination/limit behavior, which the schema covers.

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 only 60%, so the description must compensate, and it does for the most semantically important parameter: direction's three values are each defined (upstream traces suppliers, downstream traces customers, both returns both). It does not add anything for the org_id/company_id aliases or the limit, which the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource ('Return supply-chain relationships for one or more organizations'), which is clearly distinct from siblings like scrutica_get_company or scrutica_get_facility. However, it does not explicitly name or contrast against any sibling tool, so differentiation is left to inference.

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?

The description explains the meaning of each direction value (upstream=suppliers, downstream=customers, both), which implies when each mode is appropriate. But it gives no explicit when-to-use/when-not guidance or routing against the sibling tools such as scrutica_get_company or scrutica_search.

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

All Scrutica 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