Skip to main content
Glama
Sign In
sheypoor-mcp

sheypoor-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Ad details

sp_ad
Read-onlyIdempotent

Retrieve full details for a single Sheypoor ad, including description, price, location, seller, attributes, and photo links, using its ad ID.

Instructions

Get one Sheypoor ad in full: description, price, location, seller, every attribute and photo links.

city_slug and category_slug plug into sp_search; sp_similar finds comparable ads. Rentals have prices (رهن deposit, اجاره rent). The seller's phone is not available; open url to contact the seller.

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": {
      "id": "<id>"
    },
    "name": "sp_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAd id from sp_search.
photosNoPhoto URLs to include.

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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: the seller's phone is unavailable and the agent must open `url` to contact the seller, plus the rental price semantics (رهن/اجاره).

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 core purpose and kept to a few tight sentences. The city_slug/category_slug sentence is a bit tangential to this tool's own parameters but still earns its place as routing context.

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 return values, and it does so by listing the fields returned. The phone-unavailable caveat and rental price note round out what an agent needs to call and interpret it correctly.

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%, so both `id` and `photos` are already documented, and the description adds little about them. The mention of `city_slug` and `category_slug` is slightly confusing since those are not parameters of this tool, and the `photos` count parameter is not elaborated in the description.

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 ('Get one Sheypoor ad in full') and enumerates the returned fields (description, price, location, seller, attributes, photo links), which clearly separates it from list-oriented siblings like sp_search and sp_similar.

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?

It points to sp_search for discovery and sp_similar for comparable ads, implying this tool is for fetching a single known ad's full detail. It never states an explicit 'use this when' rule, but the routing context is clear enough.

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