Skip to main content
Glama
Sign In
sheypoor-mcp

sheypoor-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Similar ads

sp_similar
Read-onlyIdempotent

Compares an ad with similar listings in the same city and category, filtered by price range, to help assess whether its asking price is low or high.

Instructions

Find ads comparable to one ad: same city and deepest category (car model...), price within a percent band.

Use it to judge whether an ad is cheap or dear. With fewer than 3 matches it widens to the parent category (shown in category). Rentals and ads without a numeric price match by category only. Newest first; the ad itself and paid showcase ads are left out.

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

Input Schema

NameRequiredDescriptionDefault
idYesAd id from sp_search.
limitNoMax ads.
price_range_pctNoKeep ads within this percent of the ad's price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

The description goes far beyond the standard annotations by detailing filtering logic, specifically that the ad itself and paid showcase ads are excluded, and that it filters rentals/ads without numeric prices differently. This provides rich behavioral context for the agent.

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?

The description is dense and highly packed with operational rules. While slightly rambling, every sentence serves a critical purpose in defining tool behavior, making it highly effective despite its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of multi-criteria matching, filtering, and fallback logic, the description is extremely complete. It handles all the nuances an AI agent would need to execute this comparison correctly.

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?

Since schema coverage is 100%, the baseline is high. The description adds value by defining the parameters contextually, clarifying that the 'id' is an 'Ad id from sp_search' and framing the 'price_range_pct' as being relative to the targeted ad's price.

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?

The description clearly states the purpose is to 'Find ads comparable to one ad' and specifies the core comparison criteria: same city, deepest category, and price within a specific percent band.

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?

It provides explicit guidance on when to use the tool ('judge whether an ad is cheap or dear') and details complex operational scenarios, such as widening the search to the parent category when fewer than 3 matches are found.

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