SupplySlate

search_suppliers

Read-onlyIdempotent

Search source-backed public supplier profiles by product category, brand, company type, service, compressor type, industry, or text. No authentication required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Text contained in a supplier name, summary, or listed brand.
`brand`	No	Exact publicly listed brand, such as Atlas Copco.
`limit`	No
`offset`	No
`country`	No	Two-letter country code. Defaults to US; use all only when broader coverage is intentional.	US
`service`	No
`category`	No	Exact category code from list_supplier_taxonomy.
`industry`	No
`company_type`	No
`compressor_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`count`	No
`total`	No

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behaviors. The description adds value by disclosing that no authentication is required and that profiles are 'source-backed public,' providing context beyond the annotations without contradiction.

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?

The description is a single, front-loaded sentence that immediately states the verb and object, then lists the search facets and ends with a critical usage note. No wasted words.

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?

Given the schema's detailed parameter definitions and an output schema, the description is sufficient for an agent to select and invoke the tool. It could mention pagination or default country, but those are already documented in the schema, so the description's brevity is acceptable.

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?

The description lists the searchable dimensions (product category, brand, company type, service, compressor type, industry, text), which maps to most of the parameters and adds meaning beyond the schema's 40% individual field descriptions. Limit and offset are conventional and need no additional explanation.

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 action ('Search') and the resource ('source-backed public supplier profiles'), and enumerates the specific search dimensions (product category, brand, company type, service, compressor type, industry, text). This distinguishes it from sibling tools like search_products or get_supplier.

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?

The description provides clear context for use: it searches public, source-backed supplier profiles and explicitly notes 'No authentication required.' However, it does not name alternative tools or specify when not to use this tool, keeping it a step below the highest bar.

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

All SupplySlate tools Inspect

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

A3.6/5.0

Disambiguation5/5

Every tool targets a distinct resource, role, or action. For example, list_orders versus list_supplier_orders clearly separates buyer and supplier views, and update_supplier_order versus update_supplier_order_issue versus update_supplier_order_return handle different concerns despite similar names. Rich descriptions eliminate ambiguity.

Naming Consistency5/5

All tool names consistently use snake_case with a verb_noun pattern (e.g., create_project, list_orders, update_supplier_capabilities, search_products). The style is uniform across reads, writes, lists, and searches, making the API predictable.

Tool Count1/5

With 55 tools, the server far exceeds the typical well-scoped range of 3-15. Even for a broad supply chain platform, 50+ tools hits the rubric's 'extreme mismatch' threshold. The domain is comprehensive, but the sheer number overwhelms and likely complicates agent tool selection.

Completeness5/5

The tool surface covers the full lifecycle from project creation, BOM management, sourcing, quoting, planning, checkout handoff, orders, returns, issues, warranties, catalog updates, supplier profiles, and validation. It handles buyer and supplier sides with appropriate state transitions, and includes meta tools for connection and schema guidance. No obvious critical gaps exist.

Resources

Need Help?