Skip to main content
Glama
Sign In
sheypoor-mcp

sheypoor-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Internet shops

sp_shops
Read-onlyIdempotent

List Sheypoor shops and agencies by city and top-level category, returning slugs for fetching detailed shop information.

Instructions

List Sheypoor's internet shops and agencies (real-estate offices, car dealers...) in a city and group.

Call sp_shop with a shop slug for details. category is a top-level group, not a sub-category such as car. Shops with no ads are left out, so a page may hold fewer than limit.

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_shops"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or province slug from sp_cities, e.g. tehran. 'iran' = all Iran.iran
pageNoPage.
limitNoShops per page.
categoryNoTop-level group slug from sp_categories, e.g. real-estate, vehicles. Omit for all.

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 read-only, idempotent, open-world, non-destructive, so safety is covered. The description adds genuinely useful behavior not in structured data: shops with no ads are omitted, so a page can contain fewer results than `limit` implies. It does not mention the page ceiling or total counts, which would have been a further improvement.

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?

Three short sentences, front-loaded with the core purpose and then the sibling pointer and the pagination caveat. No filler; only the parenthetical example list is slightly expendable.

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 four-parameter, read-only listing tool with no output schema, the description covers what it lists, how to drill into a result, and the one non-obvious result-set behavior. An agent could call it correctly from this; only result shape (fields returned per shop) is left unstated, which is acceptable since there is no output schema to lean on.

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%, so the schema already documents all four parameters, including that category comes from sp_categories and that 'iran' means all Iran. The description's clarification that `category` is a top-level group and not a sub-category such as car adds some meaning but largely restates the schema's own wording, so 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?

Specific verb and resource: "List Sheypoor's internet shops and agencies" scoped to a city and group, with concrete examples (real-estate offices, car dealers). It also names the sibling sp_shop as the details path, so an agent can tell the browse tool from the detail tool without reading either schema.

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?

Explicitly routes to sp_shop with a slug when detail is needed, which is the main alternative an agent would confuse this with. However, it gives no guidance on when to prefer sp_search over this listing, and no exclusions or prerequisites are stated.

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