Skip to main content
Glama
Sign In
sheypoor-mcp

sheypoor-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Filters of a category

sp_filters
Read-onlyIdempotent

Lists a Sheypoor category's filters, sort orders, subcategories, and neighbourhoods so you can set valid search and price-summary options before querying.

Instructions

List the filters, sort orders, sub-categories (car brands, models) and neighbourhoods Sheypoor offers in one category.

Call before using filters in sp_search or sp_price_summary. Choice filters have a name and options {id, label}: pass {name: id}. Range filters list min/max names: pass a plain number. Yes/no filters have value '1'. subcategories slugs go in category; neighbourhoods ids go in neighbourhoods; area searches the full list by name. Prices use min_price/max_price.

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": "<category>"
    },
    "name": "sp_filters"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoPart of a neighbourhood name, e.g. پونک. Needs a city (not 'iran').
cityNoCity or province slug from sp_cities, e.g. tehran. 'iran' = all Iran.iran
categoryYesSlug from sp_categories, e.g. car, house-apartment-for-rent. A brand path (car/peugeot) lists its models.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real context by disclosing the shape of the returned filter set (choice filters with name+options, range filters with min/max names, yes/no filters with value '1'). It does not mention pagination or whether results are cached, but for a static lookup that is minor.

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 purpose and the prerequisite call ordering, then a compact mapping of filter types to argument forms. It is dense with backticked tokens but every clause carries actionable information; only the run-on packing of the second paragraph slightly hurts readability.

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 output schema, the description carries the burden of describing the return value, and it does so at a useful level of abstraction (three filter kinds and their fields). It stops short of enumerating sort orders or the full response envelope, but an agent has enough to call it and consume the result.

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, but the description goes further by explaining how the returned values map onto downstream parameters (subcategory slugs into `category`, neighbourhood ids into `neighbourhoods`, `area` matching by name, prices via min_price/max_price). That is meaning the schema alone does not convey.

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 the filters, sort orders, sub-categories ... and neighbourhoods ... in one category') and scopes it to a single category, which cleanly separates it from sp_categories and sp_cities that supply the category/city slugs.

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?

Explicitly says 'Call before using `filters` in sp_search or sp_price_summary', naming both the prerequisite ordering and the dependent siblings, so an agent knows exactly when this tool is required rather than optional.

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