kairos-signal

Find DePIN networks by name or ticker

find_networks

Read-onlyIdempotent

Looks up DePIN networks (and Bittensor subnets) that have live data, by name or ticker, e.g. 'akash', 'helium', 'FIL'. Returns symbol, name, category and the network's public page. Use it to get the symbol that get_network, get_metric_history and verify_value take; a network with no public ticker is listed under its internal reference (symbol_kind 'internal_ref'). Read-only, no key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_networks"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results (default 20).
`query`	No	Name or ticker fragment, case-insensitive. Omit to list.
`category`	No	Optional category filter, e.g. compute, storage, wireless, AI.

Output Schema

Name	Required	Description	Default
`matches`	Yes
`networks`	Yes
`returned`	Yes
`networks_searched`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026
- addedOutput schema / properties / networks / items / properties / symbol_kind
```
Added value: +{
+  "enum": [
+    "ticker",
+    "internal_ref"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / networks_searched
```
Added value: +{
+  "type": "integer"
+}
```
AddedOct 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond them: results are limited to networks with live data, no API key is required, and networks without public tickers appear under an internal reference.

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 dense, front-loaded sentences with no filler. Purpose, return shape, downstream use, and the internal_ref edge case are all communicated efficiently.

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?

The tool is simple, the schema fully documents parameters, and an output schema exists, so return values need not be detailed. The description covers the key edge case (internal_ref) and the intended follow-up tools, making it complete for correct invocation.

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 the schema already documents query, category, and limit. The description reinforces query semantics with examples and explains the internal_ref symbol kind, but does not add syntax or behavior for category or limit beyond the 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?

The description uses a specific verb and resource: looks up DePIN networks and Bittensor subnets by name or ticker. It gives concrete examples ('akash', 'helium', 'FIL') and states the returned fields, making the tool clearly distinguishable from siblings.

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 explicitly says to use this tool to get the symbol required by get_network, get_metric_history, and verify_value, routing the agent to the correct downstream tools. It also explains the internal_ref fallback for networks without a public ticker.

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

All kairos-signal 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.