InfraNode

by dev.infranode

Overview Discussions Admin

Data Sources

sources

Read-onlyIdempotent

List all data sources with license, attribution and availability.

Takes no arguments. Shows which upstream sources InfraNode bundles and whether each is currently active. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 17, 2026
- addedOutput schema / $defs / ToolMeta / properties / note
```
Added value: +{
+  "type": "string"
+}
```
Changed11 schema fields changedJul 2, 2026
- removedInput schema / title
```
Removed value: -"sourcesArguments"
```
- removedOutput schema / $defs / ToolMeta / description
```
Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
```
- removedOutput schema / $defs / ToolMeta / properties / attribution / title
```
Removed value: -"Attribution"
```
- removedOutput schema / $defs / ToolMeta / properties / cache_status / title
```
Removed value: -"Cache Status"
```
- removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
```
Removed value: -"Correlation Id"
```
- removedOutput schema / $defs / ToolMeta / properties / license / title
```
Removed value: -"License"
```
- removedOutput schema / $defs / ToolMeta / properties / source / title
```
Removed value: -"Source"
```
- removedOutput schema / $defs / ToolMeta / properties / source_status / title
```
Removed value: -"Source Status"
```
- removedOutput schema / $defs / ToolMeta / title
```
Removed value: -"ToolMeta"
```
- removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
- removedOutput schema / title
```
Removed value: -"ToolEnvelope"
```

Changed1 schema field changedJun 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. The description adds that it 'shows which upstream sources InfraNode bundles and whether each is currently active,' which gives useful behavioral context beyond annotations. No contradiction.

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 three short sentences with no redundancy. Every sentence adds value: first states what is listed, second confirms no arguments, third adds behavioral insight.

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

Completeness5/5

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

Given 0 parameters, rich annotations, and presence of output schema (which will describe return structure), the description covers all essential behavioral aspects: data listed, argument needs, purpose. Complete for this simple tool.

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

Parameters4/5

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

Input schema has 0 parameters, so no parameter documentation is needed. The description's claim 'takes no arguments' is basic but sufficient confirmation for the agent.

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 clearly states the tool lists data sources and specifies the included attributes (license, attribution, availability). It distinguishes itself from sibling tools like 'air_quality' or 'weather' which likely access specific data, not the source catalog.

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?

The description says 'takes no arguments,' which sets boundaries. However, it does not explicitly state when to use this tool instead of siblings, e.g., to discover available datasets before querying specific ones. The 'read-only' note subtly implies safe usage.

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

All InfraNode 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.