Divar Intelligence MCP

dv_locate

Read-onlyIdempotent

Resolve coordinates to city or district using the public place endpoint; accuracy depends on source data.

Instructions

Resolve a point's city/district using the public place endpoint; location accuracy is source-dependent.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "dv_locate"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes
`lon`	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

B3.1/5.0

Behavior3/5

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

The annotations already declare this as read-only, idempotent, non-destructive, and open-world. The description adds a useful caveat that location accuracy is source-dependent, which goes beyond the annotations, though it does not discuss failure modes or endpoint behavior in detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted language. It efficiently states the operation and one important behavioral caveat.

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?

For a simple two-parameter lookup with rich annotations and an output schema, the description covers purpose and a reliability caveat. However, it does not compensate for the missing parameter descriptions or provide usage guidance relative to sibling tools.

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 the description must compensate. It only says 'a point' and does not explain that the parameters are latitude and longitude, their expected format, coordinate order, or the numeric bounds already shown in the schema.

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

Purpose4/5

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

The description states a specific verb and resource: resolve a point to its city/district. It is clear what the tool does, but it does not explicitly distinguish itself from similar siblings such as dv_geocode or dv_nearby.

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?

It implies the tool is for looking up a point's city/district, but gives no explicit guidance on when to use it versus alternatives or when not to use it. No sibling tool is referenced.

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