Skip to main content
Glama

Find Australian food suppliers

find_suppliers
Read-onlyIdempotent

Suppliers listed on Suppliers Net, by what they sell and where. Returns name, categories, state, a profile link, and a status: verified (claimed and ABN matched), checked, claimed, or listed (from public records). No phone numbers or email addresses are returned; the profile page says how to contact a supplier.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMost results to return. Default 25.
stateNoState code or name: NSW, VIC, QLD, SA, WA, TAS, NT, ACT. Empty for national.
categoryNoWhat they sell, e.g. 'seafood', 'lamb', 'produce'. Empty for any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive, closed-world), so the bar is lower, and the description still adds real context: the meaning of the four status values (verified/checked/claimed/listed) and the explicit statement that no phone numbers or email addresses come back. That last point is a behavioral constraint an agent would otherwise discover only after calling. It stops short of describing result ordering or how to page beyond the limit.

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?

Three tight sentences, front-loaded with the resource and scope, then returns, then the contact-detail caveat. The status taxonomy is slightly dense but each term earns its place because the values are otherwise opaque. Nothing is redundant.

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 correctly carries the return-value burden and lists the fields plus the status semantics. It also preempts the most likely follow-up question by explaining that contact details live on the profile page. Only minor gaps remain, such as total-result counts or ordering.

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 all three parameters (limit, state, category) are already documented with defaults and examples. The phrase 'by what they sell and where' loosely restates category and state but adds no syntax, format, or edge-case guidance beyond the schema. Baseline 3 is appropriate.

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 names a specific resource (suppliers listed on Suppliers Net) and the two dimensions it can be sliced by (what they sell, where). It also enumerates the returned fields, so an agent knows exactly what kind of result to expect. The sibling tools (coverage, market_rates, search_prices) are clearly different domains, and this definition leaves no ambiguity about which one answers a supplier-directory question.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the filters (category, state) make the intended query pattern obvious, but there is no explicit 'use this when...' or exclusion such as 'use search_prices instead for pricing'. An agent can infer the fit, but must do the inferring.

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