Skip to main content
Glama
Sign In
Coles and Woolworths MCP Server

Coles and Woolworths MCP Server

by whoamimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COLES_API_KEYYesAPI key for accessing the Coles API (required for Coles product searches)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_coles_productsC

Search for products at Coles.

Args:
    query: The product search query.
    store_id: The Coles store ID to search in.
    limit: Maximum number of products to return.
get_woolworths_productsC

Search for products at Woolworths.

Args:
    query: The product search query.
    limit: Maximum number of products to return.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are partitioned cleanly by retailer (Coles vs Woolworths), so an agent can pick the right one from the user's request with no ambiguity. There is no functional overlap between them.

Naming Consistency4/5

Both follow the same get_<retailer>_products snake_case pattern, which is predictable. The minor deviation is at the parameter level: Coles requires a store_id while Woolworths does not, breaking the symmetry an agent might expect.

Tool Count3/5

Two tools is thin for a server covering two retailers — essentially one operation duplicated. It is defensible for a narrowly scoped product-search server, but sits at the borderline of usefulness.

Completeness2/5

Only search is exposed: no product detail/price lookup, no store lookup or listing, and no way to resolve the store_id that get_coles_products mandates. That missing store-discovery step is a dead end that will cause agent failures on the Coles path.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources