Skip to main content
Glama

list_supplier_capability_rows

Read-onlyIdempotent

Use when the user needs valid capability/process ids, category names, tiers or required equipment specs before searching suppliers or works. This is a curated L0 dictionary from grid_capabilities.csv and equipment_types.csv; it is not a supplier list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_supplier_capability_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows, default 90.
category_idNoFilter by category id, e.g. cnc-machining.
capability_idNoFilter by exact capability row id.
equipment_typeNoEquipment type substring in English or Chinese.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing provenance (derived from two curated CSV dictionaries) and by explicitly warning that results are reference data, not suppliers, which prevents a common misuse. It does not mention pagination behavior or the default row count 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.

Conciseness4/5

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

Two sentences, front-loaded with the usage trigger and followed by a scoping disclaimer, with no filler. The file-name references ('grid_capabilities.csv', 'equipment_types.csv') are slightly implementation-facing but do establish provenance economically.

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?

For a read-only lookup tool with four optional filters and no output schema, the description covers what the rows represent, why to call it first, and what it is not. It could be stronger by stating roughly what a returned row contains field-by-field, but an agent has enough to select and invoke it 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 the four filters are already fully documented in the schema and the description adds no syntax, format, or interaction details for them. The list of returned field types loosely implies what a category or tier looks like, but this is not parameter-level guidance; baseline 3 applies.

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 description states what the tool returns (valid capability/process ids, category names, tiers, required equipment specs) and what it is not ('not a supplier list'), which separates it from search_suppliers. The verb is implicit ('list' from the name) and the 'curated L0 dictionary from grid_capabilities.csv and equipment_types.csv' phrasing leans on internal jargon, so it stops short of a crisp verb+resource statement.

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?

'Use when the user needs valid capability/process ids ... before searching suppliers or works' gives a concrete triggering condition and a sequencing rule relative to other workflows. It also carves out the negative case ('it is not a supplier list'), though it does not name the specific sibling tools to call instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources