Divar Intelligence MCP

dv_filter_schema

Read-onlyIdempotent

Discover filter types and units for a Divar listing category and city. Use it to inspect available filters, but schema presence does not guarantee source enforcement.

Instructions

Discover category filter types and units. Schema presence is not proof that the source enforces a filter.

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

Input Schema

Name	Required	Description	Default
`city`	No		tehran
`category`	Yes

Output Schema

Name	Required	Default
`data`	Yes
`warnings`	No
`schema_version`	No	1.0

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so safety is covered by structured data. The second sentence adds a genuine non-obvious caveat — that presence of a filter schema does not guarantee enforcement at the source — which is useful behavioral context beyond the annotations, though the description still omits scope or return-shape details.

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 short sentences, front-loaded with the action and capped by a caveat. There is no filler, though the first sentence is terse to the point of ambiguity.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. However, with 0% parameter coverage and a vague purpose on a discovery tool, the description leaves the inputs and the practical workflow incompletely specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both 'city' (default 'tehran') and the required 'category' are undocumented. The description implies a category is the key input but says nothing about what values are valid, what 'city' scopes, or the format expected, leaving the agent to guess both parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Discover' plus resource 'category filter types and units' gives a rough sense of a metadata-introspection tool, but it's unclear what a 'filter schema' actually is or what the tool returns. Nothing in the description distinguishes it from siblings like dv_search or dv_count, so an agent must infer its role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or alternative named. The caveat sentence hints at a prerequisite (verify the source actually enforces a filter), but the agent is left to infer that this tool should be called before relying on filter behavior.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.