Skip to main content
Glama

Brands with deals now

list_brands
Read-onlyIdempotent

List brands that have at least one current promotion in Singapore, with how many each has.

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_brands"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description usefully adds behavior annotations don't carry: the Singapore market scope, the 'at least one current promotion' inclusion threshold, and the fact that counts are returned. It does not address ordering, pagination, or how 'current' is evaluated, so it adds moderate rather than rich context.

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?

A single sentence that front-loads the verb and resource, then layers scope and output shape in order of importance. Every clause carries information; nothing is redundant with the title or annotations.

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 parameters and no output schema, the description must carry the return shape and scope, and it does ('brands... with how many each has', Singapore-only). Remaining minor gaps are result ordering and whether the list is exhaustive or truncated, which matter little for a zero-argument read-only list.

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 tool takes no parameters, which is the baseline-4 case: there is nothing for the description to disambiguate. The definition correctly reflects the empty input schema and spends no words re-explaining it.

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?

States a specific verb (list) and resource (brands) plus two scoping constraints: brands with at least one current promotion, and Singapore as the market. It also previews the payload ('how many each has'). It stops short of explicitly naming a sibling for contrast, but the brand-level aggregation is inherently distinguishable from the promotion-level siblings such as search_promotions or nearby_promotions.

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: an agent can infer this is the tool for a brand-level overview when individual promotions aren't needed. There is no explicit when-not guidance and no mention of alternatives like get_deal_list, so the agent must reason from the description alone. With zero parameters there are no prerequisites to convey, which limits the harm.

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