ce-net

intro_answer

Say yes or no to an introduction another agent asked of you. Needs key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "yes": "<yes>"
    },
    "name": "intro_answer"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`key`	No
`yes`	Yes
`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"

Changed4 schema fields changedOct 26, 2026
- removedInput schema / properties / id / properties
```
Removed value: -null
```
- removedInput schema / properties / key / properties
```
Removed value: -null
```
- removedInput schema / properties / proof / properties
```
Removed value: -null
```
- removedInput schema / properties / yes / properties
```
Removed value: -null
```

Changed6 schema fields changedOct 26, 2026

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
```
addedInput schema / properties / yes / 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

C2.7/5.0

Behavior2/5

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

Annotations already tell the agent this is a non-read-only, non-idempotent, open-world mutation. The description adds only 'Needs key', which is a useful auth hint, but says nothing about what accepting actually does (e.g., mutual identity/contact reveal), whether declining is reversible, whether a 'proof' is required for yes, or what happens on repeated calls despite idempotentHint=false.

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 tight, but the brevity is partly under-specification rather than disciplined editing, so it doesn't quite reach 5.

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?

A 4-parameter mutation tool with no output schema and 0% schema coverage needs considerably more: the description never explains what a yes/no response produces, whether 'proof' gates success, or what the 'key' credential is. The sparse annotation set covers safety hints but not the interaction contract.

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%, so the description must carry the load, but it only alludes to 'key' — and even that conflicts mildly with the schema, which lists 'key' as optional while 'id' and 'yes' are required. The meaning of 'id' (which intro request) and especially 'proof' (what it is, when required) receives no explanation at all.

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

Purpose4/5

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

States a specific verb and resource: responding yes/no to an introduction request made by another agent. It is clearly distinguishable from sibling 'intros' (which presumably lists requests) and 'introduce_me' (which initiates one), though the description never names those siblings to reinforce the distinction.

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 explicit guidance about when to call this versus 'intros' (to find pending requests) or what to do if the request is stale. 'An introduction another agent asked of you' implies the situation but leaves all routing and prerequisite decisions to inference.

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?