Skip to main content
Glama

Wafergraph MCP

by com.wafergraph

Get segment leaders

get_segment_leaders

Who runs a given layer of the semiconductor & AI supply chain: the companies at monopoly/leader market position in one taxonomy segment (or all 12 if none given), with country and market cap, plus a count of how many companies sit at each position (monopoly/leader/major/challenger/niche) in that segment. country is the company's HEADQUARTERS country only, not a manufacturing-footprint field. A company headquartered here may fabricate, assemble, or test elsewhere — do not read this data as production geography.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
segmentNoA taxonomy segment id, e.g. 'foundry', 'eda_ip' (see get_segments). Case-insensitive. Omit to cover all 12 segments.

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It clarifies that country is headquarters only, not manufacturing footprint, and mentions the count distribution. No contradictions, but could state if read-only.

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 detailed but each sentence adds unique information. It front-loads the main purpose. Slightly verbose with the country caveat, but still efficient.

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 no output schema, the description adequately covers return fields (companies, country, market cap, position counts) and addresses potential misuse (country interpretation). Complete for a single-parameter query tool.

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 100%. Description adds value by explaining segment values ('foundry', 'eda_ip'), case-insensitivity, and that omitting returns all segments. This goes beyond the schema's description.

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 clearly states the tool returns companies at monopoly/leader market positions in a taxonomy segment, with country, market cap, and counts per position. It distinguishes itself from sibling tools like get_company or filter_companies by specifying the unique output.

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?

It explains the tool's purpose and the optional segment parameter, but does not explicitly mention when to use this tool versus alternatives like get_segments or get_company. However, the context is clear enough for an AI agent.

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

All Wafergraph MCP 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.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: analyzing portfolio exposure, comparing companies, finding chokepoints, getting company details, country exposure, deals, segments, supply chain walk, and company search. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., 'get_company', 'search_companies', 'find_chokepoints'). The convention is uniform and predictable.

Tool Count5/5

9 tools is well-scoped for a specialized supply chain analysis server. Each tool serves a distinct query or analysis need without being too few or too many.

Completeness4/5

The tool set covers core operations: search, detail, comparison, portfolio analysis, chokepoint identification, country exposure, deals, and supply chain graph traversal. Minor gaps like historical trends or alerts exist but do not hinder primary use cases.

Resources