Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

thread_read

Read-onlyIdempotent

Deprecated, works until 2026-11-10: use node_read. Needs key.

Input Schema

NameRequiredDescriptionDefault
idYes
keyNo
proofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
  2. Changed2 schema fields changed
    • 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"
  3. Changed2 schema fields changed
    • 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"
  4. Changed2 schema fields changed
    • 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"
  5. Changed2 schema fields changed
    • 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"
  6. Changed2 schema fields changed
    • 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"
  7. Changed2 schema fields changed
    • 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"
  8. Changed2 schema fields changed
    • 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"
  9. Changed3 schema fields changed
    • removedInput schema / properties / id / properties
      Removed value: -null
    • removedInput schema / properties / key / properties
      Removed value: -null
    • removedInput schema / properties / proof / properties
      Removed value: -null
  10. Changed5 schema fields changed
    • addedInput schema / properties / id / properties
      Added value: +null
    • 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
  11. Changed1 schema field changed
    • 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"
  12. Changed2 schema fields changed
    • 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"
+}
  13. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds two genuinely useful facts outside the structured data: a hard deprecation cutoff date and that a key is needed — though 'Needs key' is slightly at odds with the schema marking only `id` as required, it doesn't contradict the annotations.

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?

Three terse clauses, front-loaded with the most decision-relevant fact (deprecation) and the redirect. It wastes no words, but the extreme brevity is under-specification rather than economy — the purpose of the tool never makes it in.

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 deprecated, soon-to-be-removed tool the bar is low, but an agent still needs to know what it returns (no output schema exists) and what `proof` is before invoking it. Neither is covered, and no migration detail is given for mapping the `id` to node_read's parameters.

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% across 3 parameters, so the description carries the full burden and largely fails: `id` and `proof` are never explained, and `key` is only mentioned as 'needs key' with no format or acquisition guidance. It does at least flag that an auth token is involved, which is why it isn't a 1.

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 thread_read actually does — no verb or resource is given; the only content is a deprecation notice and a pointer to node_read. An agent must infer 'read a thread' from the name alone, and it's unclear whether this reads a thread, a node thread, or a comment chain given siblings like space_thread_read and thread_graph.

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?

'Deprecated, works until 2026-11-10: use node_read' is explicit when-not-to-use guidance with a named alternative, plus a hard deadline. It falls short of 5 only because it gives no positive condition under which this tool would still be the right choice (e.g., legacy IDs).

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

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