Kairos Signal — verifiable DePIN data API

Get a network's latest measured values

get_network

Read-onlyIdempotent

Returns the latest first-party measurements for one DePIN network (GPU and CPU capacity, storage, node or hotspot counts, on-chain totals), each with value, unit, as_of, freshness and the verify_url on the network's own API that you can open to check it. Market prices are not included. metric_filter narrows by substring; stale readings are omitted unless include_stale is true. Incident/stale exclusion reasons are returned separately, without values and not counted as metrics. Read-only, no key.

Input Schema

Name	Required	Description
`symbol`	Yes	Network ticker, e.g. AKT, FIL, HNT (find_networks resolves names).
`max_metrics`	No	Max metrics returned (default 40).
`include_stale`	No	Include readings past their freshness window (default false).
`metric_filter`	No	Optional case-insensitive substring, e.g. 'gpu' or 'storage'.

Output Schema

Name	Required	Description	Default
`name`	No
`symbol`	Yes
`category`	No
`page_url`	No
`telemetry`	Yes
`stale_omitted`	No
`metrics_matched`	No
`metrics_returned`	Yes
`onchain_first_party`	Yes
`deep_network_profile`	No
`live_withheld_not_live`	No
`onchain_withheld_not_live`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026
- addedOutput schema / properties / live_withheld_not_live
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / onchain_withheld_not_live
```
Added value: +{
+  "type": "object"
+}
```
Changed2 schema fields changedOct 24, 2026
- addedOutput schema / properties / onchain_first_party / items / properties / token_contract_note
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / telemetry / items / properties / token_contract_note
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedOct 23, 2026
- addedOutput schema / properties / deep_network_profile
```
Added value: +{
+  "type": "object"
+}
```
Changed1 schema field changedOct 21, 2026
- addedInput schema / properties / symbol / examples
```
Added value: +[
+  "AKT",
+  "FIL",
+  "HNT"
+]
```
AddedOct 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/no-key, yet the description still adds real behavior: what a metric record carries (value, unit, as_of, freshness, verify_url), that incident/stale exclusion reasons come back separately without values and are not counted as metrics, and that each value is independently verifiable. It omits return shape detail, though an output schema exists.

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 dense paragraph that front-loads the returned payload and then layers the filter/stale/incident semantics. No sentence is wasted, though 'Read-only, no key' largely repeats annotations and could be dropped.

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, the description needn't detail return values and doesn't. It covers the freshness model, the exclusion-reason side channel and the verify_url, giving an agent enough to call this correctly; only sibling routing for history/name-resolution is left to other tools.

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?

Schema coverage is 100%, so baseline is 3; the description still adds semantic value by explaining that metric_filter is a substring match and that include_stale controls the freshness window rather than filtering something else. It doesn't restate max_metrics or the symbol format, which are handled in-schema.

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?

States a specific verb and resource ('returns the latest first-party measurements for one DePIN network') and enumerates the metric families covered (GPU/CPU capacity, storage, node counts, on-chain totals). It also carves out what it is not ('Market prices are not included'), which separates it from siblings like get_metric_history and check_balance.

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?

Makes the scope boundary explicit by excluding market prices and by noting stale readings are omitted unless include_stale is true, which tells the agent when to flip that flag. It doesn't name a competing sibling for historical or cross-network queries (find_networks / get_metric_history), so the alternative routing is left implicit.

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

All Kairos Signal — verifiable DePIN data API 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.