Skip to main content
Glama
Sign In
sheypoor-mcp

sheypoor-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Categories

sp_categories
Read-onlyIdempotent

List Sheypoor categories and slugs for sp_search and sp_filters, grouped under 11 top-level groups, and find matching categories by name or slug.

Instructions

List Sheypoor's categories with the slug sp_search and sp_filters take, grouped under 11 top-level groups.

Car brands and models are deeper: sp_filters(category="car") lists them (car/peugeot). Use a sub-category slug alone (car, not vehicles/car).

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

Input Schema

NameRequiredDescriptionDefault
queryNoPart of a category name or slug, e.g. خودرو.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered; the description adds real behavioral context beyond that: the result set is grouped under 11 top-level groups, and car brands/models are deliberately excluded from this listing. That exclusion is a meaningful scope boundary an agent would otherwise discover only by testing.

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 compact sentences with no filler, and the core purpose is front-loaded in the first clause. The opening phrase ('with the slug sp_search and sp_filters take') is slightly compressed in a way that costs a re-read, but nothing is wasted.

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?

There is no output schema, yet the description compensates by disclosing the return structure (grouped under 11 top-level groups) and the notable absence of car brands/models. For a one-optional-parameter read-only lookup this covers what an agent needs, though it doesn't say how deep the tree goes beyond the top level.

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 description coverage is 100% and the single 'query' parameter is already documented in the schema as a partial name/slug match with an example. The description never mentions the query parameter, so it adds no semantic value here; 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 concrete verb and resource ('List Sheypoor's categories') and immediately frames the output's purpose: it supplies the slug values that sp_search and sp_filters consume. That framing distinguishes it from every sibling, since none of the others are slug-enumeration tools.

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?

Gives a concrete routing rule for a hard case: 'Car brands and models are deeper: sp_filters(category="car") lists them' tells the agent where to go when this tool's output is insufficient. It also gives the correct slug-usage convention ('Use a sub-category slug alone (car, not vehicles/car)'), but does not state when to skip this tool entirely, e.g. if the agent already knows the slug.

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