ce-net

twins_near

Read-onlyIdempotent

Public digital twins of real places (print farms, factories, warehouses, ports, airports, streets)...

Input Schema

Name	Required	Description	Default
`lat`	No
`lon`	No
`kind`	No
`mode`	No
`place`	No
`radius_km`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 29, 2026

removedInput schema / properties / kind / description

Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"

removedInput schema / properties / mode / description

Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"

removedInput schema / properties / place / description

Removed value: -"a city or 'district, city' (e.g. 'Huaqiangbei, Shenzhen'); or give lat and lon"

removedInput schema / properties / radius_km / description
```
Removed value: -"default 100"
```

Changed4 schema fields changedOct 28, 2026

addedInput schema / properties / kind / description

Added value: +"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"

addedInput schema / properties / mode / description

Added value: +"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"

addedInput schema / properties / place / description

Added value: +"a city or 'district, city' (e.g. 'Huaqiangbei, Shenzhen'); or give lat and lon"

addedInput schema / properties / radius_km / description
```
Added value: +"default 100"
```

Changed4 schema fields changedOct 28, 2026

removedInput schema / properties / kind / description

Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"

removedInput schema / properties / mode / description

Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"

removedInput schema / properties / place / description

Removed value: -"a city or 'district, city' (e.g. 'Huaqiangbei, Shenzhen'); or give lat and lon"

removedInput schema / properties / radius_km / description
```
Removed value: -"default 100"
```

Changed4 schema fields changedOct 28, 2026

addedInput schema / properties / kind / description

Added value: +"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"

addedInput schema / properties / mode / description

Added value: +"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"

addedInput schema / properties / place / description

Added value: +"a city or 'district, city' (e.g. 'Huaqiangbei, Shenzhen'); or give lat and lon"

addedInput schema / properties / radius_km / description
```
Added value: +"default 100"
```

Changed4 schema fields changedOct 27, 2026

removedInput schema / properties / kind / description

Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"

removedInput schema / properties / mode / description

Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"

removedInput schema / properties / place / description

Removed value: -"a city or 'district, city' (e.g. 'Huaqiangbei, Shenzhen'); or give lat and lon"

removedInput schema / properties / radius_km / description
```
Removed value: -"default 100"
```

Changed4 schema fields changedOct 27, 2026

addedInput schema / properties / kind / description

Added value: +"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"

addedInput schema / properties / mode / description

Added value: +"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"

addedInput schema / properties / place / description

Added value: +"a city or 'district, city' (e.g. 'Huaqiangbei, Shenzhen'); or give lat and lon"

addedInput schema / properties / radius_km / description
```
Added value: +"default 100"
```

Changed4 schema fields changedOct 26, 2026

removedInput schema / properties / kind / description

Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"

removedInput schema / properties / mode / description

Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"

removedInput schema / properties / place / description

Removed value: -"a city or 'district, city' (e.g. 'Huaqiangbei, Shenzhen'); or give lat and lon"

removedInput schema / properties / radius_km / description
```
Removed value: -"default 100"
```

Changed4 schema fields changedOct 26, 2026

addedInput schema / properties / kind / description

Added value: +"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"

addedInput schema / properties / mode / description

Added value: +"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"

addedInput schema / properties / place / description

Added value: +"a city or 'district, city' (e.g. 'Huaqiangbei, Shenzhen'); or give lat and lon"

addedInput schema / properties / radius_km / description
```
Added value: +"default 100"
```

Changed6 schema fields changedOct 26, 2026
- removedInput schema / properties / kind / properties
```
Removed value: -null
```
- removedInput schema / properties / lat / properties
```
Removed value: -null
```
- removedInput schema / properties / lon / properties
```
Removed value: -null
```
- removedInput schema / properties / mode / properties
```
Removed value: -null
```
- removedInput schema / properties / place / properties
```
Removed value: -null
```
- removedInput schema / properties / radius_km / properties
```
Removed value: -null
```
Changed10 schema fields changedOct 26, 2026
- removedInput schema / properties / kind / description
```
Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
```
- addedInput schema / properties / kind / properties
```
Added value: +null
```
- addedInput schema / properties / lat / properties
```
Added value: +null
```
- addedInput schema / properties / lon / properties
```
Added value: +null
```
- removedInput schema / properties / mode / description
```
Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
```
- addedInput schema / properties / mode / properties
```
Added value: +null
```
- removedInput schema / properties / place / description
```
Removed value: -"a city or 'district, city' (e.g. 'Huaqiangbei, Shenzhen'); or give lat and lon"
```
- addedInput schema / properties / place / properties
```
Added value: +null
```
- removedInput schema / properties / radius_km / description
```
Removed value: -"default 100"
```
- addedInput schema / properties / radius_km / properties
```
Added value: +null
```

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / mode

Added value: +{
+  "description": "only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed",
+  "enum": [
+    "observed",
+    "recorded",
+    "simulated",
+    "mixed",
+    "undeclared"
+  ],
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

D1.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so safety is covered. The description adds nothing beyond a list of example place types: it doesn't state result ordering, whether proximity is required, defaults, or what 'near' means without lat/lon.

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

Conciseness2/5

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

It is short, but it is an under-specified sentence fragment ending in an ellipsis, not a front-loaded functional statement. Brevity here reflects missing information rather than efficiency.

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

Completeness1/5

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

For a six-parameter spatial query tool with zero schema documentation and no output schema, the description provides no operational detail. An agent cannot infer required inputs, geographic semantics, or return shape from either structured fields or prose.

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

Parameters1/5

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

Schema description coverage is 0% across six parameters (lat, lon, kind, mode, place, radius_km), and the description never mentions any of them. The enum values for 'mode' (observed, recorded, simulated, mixed, undeclared) are especially opaque and receive no explanation anywhere.

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

Purpose2/5

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

The description is a noun phrase identifying the resource ('Public digital twins of real places') rather than stating a verb or operation. The name twins_near implies a proximity query, but the description never confirms that it returns twins near a coordinate or how it differs from siblings twins_search or twins_community.

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

Usage Guidelines1/5

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

No when-to-use, when-not-to-use, or alternative guidance is present. With three closely related siblings (twin_get, twins_search, twins_community, twin_submit), the absence of routing logic leaves the agent to guess.

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

All ce-net tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?