Skip to main content
Glama

Brand and spec filters of a category

em_filters
Read-onlyIdempotent

Fetch category brand and spec filter IDs to supply valid brand_id and attributes before searching products.

Instructions

List the brands and spec filters (RAM, storage, ...) Emalls offers in one category, with their ids.

Use it before em_search for a brand or spec: pass the ids as brand_id and attributes. Top brands only; some categories have no spec groups.

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": {
      "category_id": "<category_id>"
    },
    "name": "em_filters"
  }
}

Input Schema

NameRequiredDescriptionDefault
category_idYesCategory id from em_categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / category_id / description
      Previous value: -"Category id from em_categories, e.g. 39 for mobile phones."New value: +"Category id from em_categories."
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context: results are truncated to top brands and some categories return no spec groups, so an empty or short response is expected rather than an error. It does not describe the shape of the returned structures, but the added caveats are meaningful beyond the annotations.

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?

Two short sentences, front-loaded with the purpose and followed by the usage rule and the two caveats. No filler, and every clause carries information the agent needs.

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?

For a one-parameter lookup tool this is nearly complete: it covers purpose, sequencing, and result limitations. With no output schema, the return value is only sketched ('brands and spec filters ... with their ids'), leaving the grouping of spec filters and the brand entry shape unexplained.

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% and the single parameter is already documented as 'Category id from em_categories'. The description's mention of brand_id/attributes refers to how the output is reused in em_search, not to the input, so it adds no new meaning about category_id itself; baseline 3 applies.

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: list brands and spec filters offered in one category, 'with their ids'. It also implicitly distinguishes itself from em_categories (which supplies the id) and from em_search (which consumes the ids).

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?

Explicit sequencing guidance: 'Use it before em_search for a brand or spec', plus how to use the result ('pass the ids as brand_id and attributes'). Caveats about coverage ('Top brands only; some categories have no spec groups') tell the agent when the result will be thin.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.