Criora: climate & disaster risk for any place

Read a Criora document

fetch

Read-onlyIdempotent

One Criora document as markdown, with the page to cite, by an id search returned: country:, place:,, page:methodology, page:sources, catalog:layers or catalog:indicators.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	An id search returned: country:<ISO3>, place:<latitude>,<longitude>, page:<name> or catalog:layers / catalog:indicators

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 5, 2026
- removedOutput schema / $defs / DocumentMetadata / properties / sources / description
```
Removed value: -"The data sources the text cites"
```
- removedOutput schema / $defs / DocumentMetadata / properties / updated / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedOutput schema / $defs / DocumentMetadata / properties / updated / default
```
Removed value: -null
```
- removedOutput schema / $defs / DocumentMetadata / properties / updated / description
```
Removed value: -"When the data or page last changed, ISO 8601, where that is known"
```
- addedOutput schema / $defs / DocumentMetadata / properties / updated / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / text / description
```
Removed value: -"The document as markdown"
```
- removedOutput schema / properties / url / description
```
Removed value: -"The Criora page the document is about, for citing"
```
Changed11 schema fields changedNov 2, 2026
- removedInput schema / properties / id / title
```
Removed value: -"Id"
```
- removedInput schema / title
```
Removed value: -"fetchArguments"
```
- removedOutput schema / $defs / DocumentMetadata / properties / kind / title
```
Removed value: -"Kind"
```
- removedOutput schema / $defs / DocumentMetadata / properties / sources / title
```
Removed value: -"Sources"
```
- removedOutput schema / $defs / DocumentMetadata / properties / updated / title
```
Removed value: -"Updated"
```
- removedOutput schema / $defs / DocumentMetadata / title
```
Removed value: -"DocumentMetadata"
```
- removedOutput schema / properties / id / title
```
Removed value: -"Id"
```
- removedOutput schema / properties / text / title
```
Removed value: -"Text"
```
- removedOutput schema / properties / title / title
```
Removed value: -"Title"
```
- removedOutput schema / properties / url / title
```
Removed value: -"Url"
```
- removedOutput schema / title
```
Removed value: -"FetchedDocument"
```

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / id / description

Previous value: -"An id search returned: country:<ISO3>, place:<latitude>,<longitude> or page:<name>"New value: +"An id search returned: country:<ISO3>, place:<latitude>,<longitude>, page:<name> or catalog:layers / catalog:indicators"

changedOutput schema / $defs / DocumentMetadata / properties / kind / enum

Previous value: -[
-  "country",
-  "place",
-  "page"
-]New value: +[
+  "country",
+  "place",
+  "page",
+  "catalog"
+]

AddedOct 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds genuinely new behavior: the response is markdown and includes the page to cite. It does not mention error behavior for unknown ids, but given annotation coverage that is a minor gap.

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?

A single sentence that front-loads the return value and purpose before the id-format list. Dense but every clause carries information; the trailing format list is the least valuable part since the schema already has it.

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, return values need not be spelled out, yet the description still tells the agent it gets markdown plus a citation page, and it pins the id provenance to search. For a one-parameter read tool this is essentially complete.

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% and the description's id format list (country:, place:, page:, catalog:) duplicates the schema's own enumeration almost verbatim. No additional meaning such as case sensitivity, validation rules, or ambiguity handling is added.

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?

States a specific verb (returns/fetches one document) plus the resource (a Criora document), the output format (markdown), and that the id must come from search. This separates it from siblings like search or get_country_profile. Slightly opaque because 'Criora document' is never defined, so an agent must infer the domain.

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

Usage Guidelines4/5

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

'by an id search returned' establishes the prerequisite chain clearly: call search first, then fetch. No explicit exclusions or statement of what to do instead when no id is known, which keeps it short of a 5.

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.