Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

introduce_me

Read-onlyIdempotent

Ask ce-net to introduce you to whoever can help: a factory, a maker, another agent. Needs key.

Input Schema

NameRequiredDescriptionDefault
toNo
keyNo
needYes
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. Changed4 schema fields changed
    • removedInput schema / properties / key / properties
      Removed value: -null
    • removedInput schema / properties / need / properties
      Removed value: -null
    • removedInput schema / properties / proof / properties
      Removed value: -null
    • removedInput schema / properties / to / properties
      Removed value: -null
  10. Changed7 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 / need / description
      Removed value: -"at most 600 bytes"
    • addedInput schema / properties / need / 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 / to / properties
      Added value: +null
  11. Changed2 schema fields changed
    • addedInput schema / properties / need / description
      Added value: +"at most 600 bytes"
    • 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.4/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered elsewhere. The description adds only that a key is required; it does not say whether the call merely dispatches a request, whether ce-net responds asynchronously, or how the agent should follow up (presumably via intros or intro_answer), leaving the agent unable to predict outcomes.

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 fragments, front-loaded with the action and followed by the prerequisite. 'Needs key' is terse and slightly clipped, but there is no filler.

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?

An open-world, 4-parameter tool with no output schema and no parameter documentation needs far more than two fragments, especially around what 'proof' means and how the introduction is delivered or retrieved. The description leaves the agent guessing at the request lifecycle.

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 4 parameters, so the description must compensate and it does not. It mentions 'key' (helpfully noting it is needed even though the schema lists only 'need' as required), but 'to', 'proof', and 'need' are left entirely undefined with no format or content expectations.

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?

States the verb (introduce) and the actor (ce-net) plus example targets (factory, maker, agent), which conveys the general idea of a broker-mediated introduction. But 'whoever can help' is vague about what is actually produced, and it never distinguishes itself from close siblings like intros, intro_answer, or kindly_ask.

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?

There is no statement of when to use this versus intros, intro_answer, request, or kindly_ask, all of which sit in the same social-request space. The only guidance is the prerequisite fragment 'Needs key', which is useful but not usage routing.

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