Skip to main content
Glama
Sign In
torob-mcp

torob-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search filters

tb_filters
Read-onlyIdempotent

Retrieves available subcategories, brands, price ranges, sort options, and attribute slugs for a search query or category, so you can get correct IDs before running a product search.

Instructions

Which filters exist for a query/category: sub-categories, brands, price span, sort options, attributes.

Use before tb_search for category / brand ids or the attribute slugs and values of filters.

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

Input Schema

NameRequiredDescriptionDefault
queryNoSearch text, e.g. 'لپ تاپ'.
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • removedInput schema / properties / category / description
      Removed value: -"Category id (e.g. 94)."
    • changedInput schema / properties / query / description
      Previous value: -"Search text whose filters you want, e.g. 'لپ تاپ'."New value: +"Search text, e.g. 'لپ تاپ'."
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and determinism are covered. The description adds useful output-shape context (it returns attribute slugs/values usable as filter inputs) but says nothing about empty results, latency, or whether filters are query-dependent versus category-dependent.

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?

Two short sentences, front-loaded with the return payload followed by the usage rule; nothing is padding. The first sentence is a fragment without a verb, which is slightly clipped but still readable.

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 two optional params, no output schema, and rich annotations, the definition covers the essentials: what the call yields and how to use the result in a follow-up search. The remaining gap is the undocumented `category` parameter and the interaction between the two optional inputs.

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 only 50%: `query` has a description and example in Farsi, while `category` is an undescribed integer. The phrase "category / brand ids" hints that `category` consumes an id rather than a name, which is real added meaning, but it never states where that id comes from (tb_category) or how query and category interact when both are supplied.

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?

The description names the specific resource and enumerates the payload: sub-categories, brands, price span, sort options, and attributes returned for a query/category. It implicitly distinguishes itself from tb_search by being the metadata-discovery step, though it never explicitly says it does not return products.

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

Usage Guidelines4/5

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

"Use before tb_search for category / brand ids or the attribute slugs and values" gives a clear sequencing rule and names the downstream sibling, which is stronger than most definitions. It stops short of covering edge cases such as calling with neither query nor category, or when to prefer tb_category/tb_brands for ids instead.

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

Deploy Server

Other Tools