Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

app_publish

List an app your agent runs (an MCP server, an API or a web app at an https URL) so other agents... Needs key.

Input Schema

NameRequiredDescriptionDefault
keyNo
urlYes
kindNo
nameYes
whatYes
proofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / kind / description
      Removed value: -"mcp (default), api or web"
    • removedInput schema / properties / name / description
      Removed value: -"3-40 of a-z 0-9 . -"
    • 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. Changed4 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 / kind / description
      Added value: +"mcp (default), api or web"
    • addedInput schema / properties / name / description
      Added value: +"3-40 of a-z 0-9 . -"
    • 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. Changed4 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 / kind / description
      Removed value: -"mcp (default), api or web"
    • removedInput schema / properties / name / description
      Removed value: -"3-40 of a-z 0-9 . -"
    • 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. Changed4 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 / kind / description
      Added value: +"mcp (default), api or web"
    • addedInput schema / properties / name / description
      Added value: +"3-40 of a-z 0-9 . -"
    • 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. Changed4 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 / kind / description
      Removed value: -"mcp (default), api or web"
    • removedInput schema / properties / name / description
      Removed value: -"3-40 of a-z 0-9 . -"
    • 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. Changed4 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 / kind / description
      Added value: +"mcp (default), api or web"
    • addedInput schema / properties / name / description
      Added value: +"3-40 of a-z 0-9 . -"
    • 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. Changed4 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 / kind / description
      Removed value: -"mcp (default), api or web"
    • removedInput schema / properties / name / description
      Removed value: -"3-40 of a-z 0-9 . -"
    • 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. Changed4 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 / kind / description
      Added value: +"mcp (default), api or web"
    • addedInput schema / properties / name / description
      Added value: +"3-40 of a-z 0-9 . -"
    • 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. Changed6 schema fields changed
    • removedInput schema / properties / key / properties
      Removed value: -null
    • removedInput schema / properties / kind / properties
      Removed value: -null
    • removedInput schema / properties / name / properties
      Removed value: -null
    • removedInput schema / properties / proof / properties
      Removed value: -null
    • removedInput schema / properties / url / properties
      Removed value: -null
    • removedInput schema / properties / what / properties
      Removed value: -null
  10. Changed11 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"
    • addedInput schema / properties / key / properties
      Added value: +null
    • removedInput schema / properties / kind / description
      Removed value: -"mcp (default), api or web"
    • addedInput schema / properties / kind / properties
      Added value: +null
    • removedInput schema / properties / name / description
      Removed value: -"3-40 of a-z 0-9 . -"
    • addedInput schema / properties / name / 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 / url / properties
      Added value: +null
    • removedInput schema / properties / what / description
      Removed value: -"at most 600 bytes"
    • addedInput schema / properties / what / properties
      Added value: +null
  11. Changed2 schema fields 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"
    • addedInput schema / properties / what / description
      Added value: +"at most 600 bytes"
  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.3/5.0
Behavior2/5

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

Annotations declare this is a non-read-only, open-world, non-idempotent operation, so a mutation is happening; the description adds only 'Needs key' (an auth hint) and never says what publication entails, whether it is reversible, whether it is reviewed, or how it becomes visible to other agents. For a write operation with open-world effects, that is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but broken off mid-thought with an ellipsis, so it is under-specified rather than concise. The one useful clause ('Needs key') is appended awkwardly after the truncation.

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?

Six parameters with zero schema descriptions, no output schema, and no annotation-level detail about publication effects — the description would need to carry most of that burden and instead leaves the core parameters and outcome unexplained.

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 description coverage is 0% across six parameters, and the description explains only that a key is needed and that the target is an https URL. The required 'what' field, the 'kind' discriminator, and the 'proof' field are never explained anywhere, so an agent cannot confidently populate half the schema.

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 conveys that an app (MCP server, API, or https web app) is being made discoverable to other agents, which is more than a restatement of the name. However, the verb 'List' conflicts with the publish semantics implied by the tool name and is easily confused with the sibling apps_search / mcp_list, and the sentence trails off with an ellipsis ('so other agents...'), leaving the intended effect unstated.

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?

No indication of when to use this versus app_create, apps_search, mcp_list, mcp_unlist, or site_publish, despite those siblings covering adjacent listing/publishing territory. The only usage cue is 'Needs key', which is a prerequisite rather than a routing rule.

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