Criora: climate & disaster risk for any place

Find a place

find_place

Read-onlyIdempotent

Candidate places for a name, best match first, each with coordinates, full name and kind (city, island, volcano...).

Call it only when a name is ambiguous (several Springfields) or one place is used in several calls: every place tool takes a name itself and uses its best match. GeoNames gazetteer in every language; no street addresses.

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": {
      "query": "<query>"
    },
    "name": "find_place"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many candidates to return
`query`	Yes	A place name in any language or script, optionally followed by the region or country it lies in after a comma: Springfield, Missouri
`language`	No	Language code for the name of the place found (resolved_from); the rest of the answer is English	en

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 5, 2026
- removedOutput schema / $defs / Place / properties / display_name / description
```
Removed value: -"The full name, with the region and country"
```
- removedOutput schema / $defs / Place / properties / kind / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedOutput schema / $defs / Place / properties / kind / description
```
Removed value: -"What the name is: city, town, village, state, country, island and so on"
```
- addedOutput schema / $defs / Place / properties / kind / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / $defs / Place / properties / spelled / description
```
Removed value: -"Found by a name spelled nearly like the one asked, not by that name"
```

Changed16 schema fields changedNov 2, 2026

addedInput schema / properties / language

Added value: +{
+  "default": "en",
+  "description": "Language code for the name of the place found (resolved_from); the rest of the answer is English",
+  "enum": [
+    "en",
+    "de",
+    "fr",
+    "it",
+    "es",
+    "nl",
+    "pl",
+    "uk",
+    "ro",
+    "sr",
+    "ru"
+  ],
+  "type": "string"
+}

removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```

changedInput schema / properties / query / description

Previous value: -"A place name or address, in any language"New value: +"A place name in any language or script, optionally followed by the region or country it lies in after a comma: Springfield, Missouri"

removedInput schema / properties / query / title
```
Removed value: -"Query"
```
removedInput schema / title
```
Removed value: -"find_placeArguments"
```
removedOutput schema / $defs / Place / properties / display_name / title
```
Removed value: -"Display Name"
```

changedOutput schema / $defs / Place / properties / kind / description

Previous value: -"What the name is: city, state, road and so on"New value: +"What the name is: city, town, village, state, country, island and so on"

removedOutput schema / $defs / Place / properties / kind / title
```
Removed value: -"Kind"
```
removedOutput schema / $defs / Place / properties / latitude / title
```
Removed value: -"Latitude"
```
removedOutput schema / $defs / Place / properties / longitude / title
```
Removed value: -"Longitude"
```
removedOutput schema / $defs / Place / properties / name / title
```
Removed value: -"Name"
```

addedOutput schema / $defs / Place / properties / spelled

Added value: +{
+  "description": "Found by a name spelled nearly like the one asked, not by that name",
+  "type": "boolean"
+}

changedOutput schema / $defs / Place / required

Previous value: -[
-  "name",
-  "display_name",
-  "latitude",
-  "longitude",
-  "kind"
-]New value: +[
+  "name",
+  "display_name",
+  "latitude",
+  "longitude",
+  "kind",
+  "spelled"
+]

removedOutput schema / $defs / Place / title
```
Removed value: -"Place"
```
removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
removedOutput schema / title
```
Removed value: -"find_placeOutput"
```

Changed4 schema fields changedOct 13, 2026

addedOutput schema / $defs

Added value: +{
+  "Place": {
+    "additionalProperties": false,
+    "properties": {
+      "display_name": {
+        "description": "The full name, with the region and country",
+        "title": "Display Name",
+        "type": "string"
+      },
+      "kind": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "What the name is: city, state, road and so on",
+        "title": "Kind"
+      },
+      "latitude": {
+        "title": "Latitude",
+        "type": "number"
+      },
+      "longitude": {
+        "title": "Longitude",
+        "type": "number"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "display_name",
+      "latitude",
+      "longitude",
+      "kind"
+    ],
+    "title": "Place",
+    "type": "object"
+  }
+}

addedOutput schema / properties / result / items / $ref
```
Added value: +"#/$defs/Place"
```
removedOutput schema / properties / result / items / additionalProperties
```
Removed value: -true
```
removedOutput schema / properties / result / items / type
```
Removed value: -"object"
```

First observedSep 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the description focuses on value-add: results are ranked best-match-first, each carries coordinates/name/kind, and the source is a GeoNames gazetteer in every language. It also sets a scope boundary ('no street addresses'), which prevents wasted calls, though it says nothing about ambiguity resolution when no match exists.

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?

Two sentences, front-loaded with what is returned before the conditional usage rule. Parentheticals are short and illustrative rather than padding; nothing is redundant with the title or annotations.

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 an output schema present and full schema descriptions, the description only needs to justify existence and routing, which it does well, including the gazetteer source and address limitation. Minor gap: it does not mention what happens on zero results or how the language parameter affects only the resolved name field.

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 description coverage is 100%, so query, limit, and language are fully documented in the schema itself. The description only reinforces the name-language notion ('in every language') and the ranking implied by limit, adding little beyond the structured fields — baseline 3 applies.

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 names the specific resource and result shape: 'Candidate places for a name, best match first, each with coordinates, full name and kind (city, island, volcano...)'. It also distinguishes itself from the many sibling tools by noting every other place tool resolves a name on its own, so an agent can tell when this one is needed without inspecting the schema.

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 gives an explicit when-to-use rule ('only when a name is ambiguous (several Springfields) or one place is used in several calls') and implicitly tells the agent not to call it for single unambiguous lookups. The two triggering conditions are concrete and actionable.

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

All Criora: climate & disaster risk for any place 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.