Skip to main content
Glama

Wafergraph MCP

by com.wafergraph

Get subsegment

get_subsegment

All companies in one segment+subsegment pair, as compact refs sorted by market cap descending, plus a market_position breakdown and a country breakdown computed over the FULL matching set (not just the returned page). Use list_subsegments first if you don't know valid segment/subsegment ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax companies to return, 1-100. Default 50.
offsetNoCompanies to skip, for paging past the first `limit`. Default 0.
segmentYesTaxonomy segment id, e.g. 'equipment_front_end' (see get_segments).
subsegmentYesTaxonomy subsegment id within that segment, e.g. 'litho' (see list_subsegments).

TDQS

A4.5/5.0
Behavior4/5

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

Despite no annotations, the description discloses key behaviors: returns compact refs, sorted by market cap descending, computes breakdowns over the full set (not just page). It adds context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: one comprehensive sentence covering output and behavior, one sentence with prerequisite guidance. No wasted words.

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 fully explains the return structure (compact refs, breakdowns), sorting, pagination implication (breakdowns over full set), and prerequisites. Complete for a retrieval tool.

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%, so baseline is 3. The description adds context by referencing get_segments and list_subsegments for valid segment/subsegment IDs, but does not add new meaning beyond schema descriptions for limit/offset.

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 all companies in a segment+subsegment pair as compact refs sorted by market cap descending, with market_position and country breakdowns. It distinguishes from sibling tools like list_subsegments.

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?

Explicitly advises to use list_subsegments first if segment/subsegment IDs are unknown, providing direct guidance on when to use this tool vs alternatives.

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