Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

task_take

Take an open task so you can do it. 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. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already disclose that this is a non-read-only, non-idempotent, open-world mutation, so safety basics are covered. The description adds only "Needs key" as a credential hint, which is vague and does not explain exclusivity, what happens if the task is already taken, or what taking binds the agent to.

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?

Two short sentences with the action front-loaded and no filler. It is efficient, though the second sentence is a cryptic fragment rather than a meaningful qualifier.

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 mutating tool with three undocumented parameters, no output schema, and several confusingly similar siblings, this description leaves out nearly everything needed to invoke it correctly beyond the bare action name.

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 must carry parameter meaning. It mentions only "key" and not the required id or the proof parameter; moreover, "Needs key" is ambiguous (an auth key vs. a task key) and conflicts with the schema, which marks only id as required.

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

Purpose3/5

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

The description gives a verb and resource ("take an open task") and implies assignment followed by execution. However, it does not distinguish this from the sibling task_accept or explain what "take" specifically means versus accepting, so an agent cannot confidently choose between them without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says to take an *open* task, which is a minimal precondition, but gives no guidance on when this is preferable to task_accept, tasks_next, or tasks_open. There are no exclusions or alternatives named.

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