Skip to main content
Glama

Find brands by email frequency

find_brands
Read-onlyIdempotent

Ecommerce brands StackEnhance Signal tracks in one market, ranked by current email frequency (average marketing emails per week over the last 90 days), optionally within a category such as "Fashion & Apparel" or "Home & Interior". Use for questions like "Which brands email most frequently in Swedish ecommerce?" or to find a brand when the user names a kind of brand ("a Swedish fashion brand"). Rankings are available for SE, NO, DK, FI and DE only; market is a country, never a topic. Brands with too little observed data are left out of rankings. To then compare some of the brands (or brands the user named), call compare_brands with their names. Returns brand names, categories and emails per week only. Each brand has a details_url to cite.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>"
    },
    "name": "find_brands"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many brands to return (1-10, default 10).
marketYesCountry as a two-letter code (SE, NO, DK, FI or DE) or its name ("Sweden"). Not a topic or category: put that in `category`.
categoryNoOptional category, e.g. "Fashion & Apparel", "Home & Interior", "Beauty & Cosmetics", "Sports & Outdoor".

Output Schema

NameRequiredDescriptionDefault
brandsYes
marketYes
categoryYes
window_daysYes
brands_trackedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Country as a two-letter code (SE, NO, DK, FI or DE) or its name (\"Sweden\")."New value: +"Country as a two-letter code (SE, NO, DK, FI or DE) or its name (\"Sweden\"). Not a topic or category: put that in `category`."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-open-world behavior, so the description adds substantive context instead of repeating it: the five supported markets, the exclusion of brands with too little observed data, and the explicit note that market is a country and never a topic. It also constrains the return surface (names, categories, emails per week) and points to details_url for citation.

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?

Front-loaded with the core purpose, then examples, then constraints, then the sibling handoff — a sensible reading order with no filler sentences. The market-is-not-a-topic point appears twice (description and schema), which is mild redundancy but defensible as a guarding against a common mistake.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with an output schema and full annotation coverage, the description covers everything an agent needs: supported markets, exclusion rules, ranking basis, output fields, and the natural next tool. Nothing material is left to inference.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by reinforcing the market-vs-category distinction with a concrete failure mode ('market is a country, never a topic') and by naming the ranking metric that gives the results meaning. It doesn't add format or syntax detail for limit or category beyond what the schema already states.

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 — brands tracked by StackEnhance Signal in one market — plus the ranking key (average marketing emails per week over 90 days). The scope and ordering are defined tightly enough that an agent can distinguish it from compare_brands and get_brand_email_frequency without opening their schemas.

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 concrete example questions ('Which brands email most frequently in Swedish ecommerce?'), covers the indirect case ('user names a kind of brand'), and explicitly routes follow-up comparison work to compare_brands with brand names. Both when-to-use and which-alternative are spelled out.

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