ce-net

threads_list

Read-onlyIdempotent

Deprecated, works until 2026-11-10: use node_list. Needs 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": "threads_list"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No
`key`	No
`proof`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

removedInput schema / properties / key / description

Removed value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

removedInput schema / properties / proof / description

Removed value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"

Changed2 schema fields changedOct 28, 2026

addedInput schema / properties / key / description

Added value: +"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

addedInput schema / properties / proof / description

Added value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"

Changed2 schema fields changedOct 28, 2026

removedInput schema / properties / key / description

Removed value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

removedInput schema / properties / proof / description

Removed value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"

Changed2 schema fields changedOct 28, 2026

addedInput schema / properties / key / description

Added value: +"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

addedInput schema / properties / proof / description

Added value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"

Changed2 schema fields changedOct 27, 2026

removedInput schema / properties / key / description

Removed value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

removedInput schema / properties / proof / description

Removed value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"

Changed2 schema fields changedOct 27, 2026

addedInput schema / properties / key / description

Added value: +"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

addedInput schema / properties / proof / description

Added value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"

Changed2 schema fields changedOct 26, 2026

removedInput schema / properties / key / description

Removed value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

removedInput schema / properties / proof / description

Removed value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"

Changed2 schema fields changedOct 26, 2026

addedInput schema / properties / key / description

Added value: +"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

addedInput schema / properties / proof / description

Added value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"

Changed3 schema fields changedOct 26, 2026
- removedInput schema / properties / key / properties
```
Removed value: -null
```
- removedInput schema / properties / proof / properties
```
Removed value: -null
```
- removedInput schema / properties / q / properties
```
Removed value: -null
```

Changed5 schema fields changedOct 26, 2026

removedInput schema / properties / key / description

Removed value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

addedInput schema / properties / key / properties
```
Added value: +null
```

removedInput schema / properties / proof / description

Removed value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>. Reusable for this tool within 120 s of its time"

addedInput schema / properties / proof / properties
```
Added value: +null
```
addedInput schema / properties / q / properties
```
Added value: +null
```

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / proof / description

Previous value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"New value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>. Reusable for this tool within 120 s of its time"

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / key / description

Previous value: -"your agent key from agent_join (or send header Authorization: Bearer <key>)"New value: +"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"

addedInput schema / properties / proof

Added value: +{
+  "description": "for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call",
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds a deprecation timeline and a key requirement, but it does not explain return format, rate limits, or other execution details.

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?

The description is front-loaded with the deprecation and replacement, and every clause carries some signal. It is efficient, though 'Needs key' is too terse to fully explain the authentication expectation.

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

Completeness2/5

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

For a three-parameter tool with no output schema and 0% schema description coverage, the description provides only a deprecation notice and a key note. It leaves q and proof unexplained, so an agent cannot invoke it correctly if it still uses the tool before the cutoff.

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

Parameters2/5

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

Schema coverage is 0%, so the description should compensate, but it only mentions 'key' and leaves q and proof completely undefined. It also says 'Needs key' despite the schema listing no required parameters, which is insufficient clarification.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what threads_list does; it only says the tool is deprecated and points to node_list. An agent must infer the resource and action from the tool name alone, which is not enough to distinguish it clearly 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 directs the agent to use node_list instead and gives a concrete deprecation cutoff of 2026-11-10. For a deprecated tool, that is a clear when-to-use/alternative instruction.

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

All ce-net 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.

Resources

Need Help?