Skip to main content
Glama

get_supplier

Read-onlyIdempotent

Use when the user has a supplier_id or slug and needs the full public profile: location, capabilities, tolerances, materials, batch range, certifications, logo, equipment types (aggregated), and up to 20 recent works with image URLs. Contact email and phone are never returned. Use search_suppliers first if the supplier is unknown.

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": "get_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoCanonical supplier slug.
supplier_idNoPublic supplier id, e.g. sup_...

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description doesn't need to restate safety. It adds real value beyond them by disclosing a privacy boundary (contact email and phone are never returned) and a result cap (up to 20 recent works, with image URLs), which affect what the agent can promise the user. It stops short of covering invalid-id behavior or whether results are ever truncated.

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?

Front-loads the trigger condition, then the payload, then the privacy caveat and the sibling routing in descending priority. Two short sentences plus the enumeration, with no filler or restatement of the title.

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 burden of describing return content, and it does so thoroughly, including what is deliberately omitted. The only gap is error behavior for an unknown or stale identifier, which matters for a lookup-by-id 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% with both slug and supplier_id documented in the schema, so the baseline applies. The description adds one useful nuance the schema does not state: the two are alternatives ("a supplier_id or slug"), i.e. either identifier suffices. It does not address what happens when both or neither are supplied.

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?

States a specific verb and resource (fetch a supplier's full public profile) and enumerates exactly what is returned: location, capabilities, tolerances, materials, batch range, certifications, logo, aggregated equipment types, and up to 20 recent works. This is clearly distinguishable from the sibling search_suppliers, which is explicitly framed as the discovery step.

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?

Gives an explicit precondition (the user already has a supplier_id or slug) and an explicit exclusion with the alternative named: "Use search_suppliers first if the supplier is unknown." The agent has no ambiguity about which of the two tools to call.

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