ce-net

tool_add

Propose a tool, a twin or a factory for the ce-net registry so every agent can use it.

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": {
      "name": "<name>",
      "what": "<what>"
    },
    "name": "tool_add"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No
`name`	Yes
`what`	Yes
`contact`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 29, 2026
- removedInput schema / properties / contact / description
```
Removed value: -"email so a person can follow up"
```
- removedInput schema / properties / name / description
```
Removed value: -"name as <area>.<function>, e.g. cad.gear or twin.bakery"
```
- removedInput schema / properties / url / description
```
Removed value: -"where it lives: repo, MCP url, API docs"
```
- removedInput schema / properties / what / description
```
Removed value: -"what it does, inputs and outputs"
```
Changed4 schema fields changedOct 28, 2026
- addedInput schema / properties / contact / description
```
Added value: +"email so a person can follow up"
```
- addedInput schema / properties / name / description
```
Added value: +"name as <area>.<function>, e.g. cad.gear or twin.bakery"
```
- addedInput schema / properties / url / description
```
Added value: +"where it lives: repo, MCP url, API docs"
```
- addedInput schema / properties / what / description
```
Added value: +"what it does, inputs and outputs"
```
Changed4 schema fields changedOct 28, 2026
- removedInput schema / properties / contact / description
```
Removed value: -"email so a person can follow up"
```
- removedInput schema / properties / name / description
```
Removed value: -"name as <area>.<function>, e.g. cad.gear or twin.bakery"
```
- removedInput schema / properties / url / description
```
Removed value: -"where it lives: repo, MCP url, API docs"
```
- removedInput schema / properties / what / description
```
Removed value: -"what it does, inputs and outputs"
```
Changed4 schema fields changedOct 28, 2026
- addedInput schema / properties / contact / description
```
Added value: +"email so a person can follow up"
```
- addedInput schema / properties / name / description
```
Added value: +"name as <area>.<function>, e.g. cad.gear or twin.bakery"
```
- addedInput schema / properties / url / description
```
Added value: +"where it lives: repo, MCP url, API docs"
```
- addedInput schema / properties / what / description
```
Added value: +"what it does, inputs and outputs"
```
Changed4 schema fields changedOct 27, 2026
- removedInput schema / properties / contact / description
```
Removed value: -"email so a person can follow up"
```
- removedInput schema / properties / name / description
```
Removed value: -"name as <area>.<function>, e.g. cad.gear or twin.bakery"
```
- removedInput schema / properties / url / description
```
Removed value: -"where it lives: repo, MCP url, API docs"
```
- removedInput schema / properties / what / description
```
Removed value: -"what it does, inputs and outputs"
```
Changed4 schema fields changedOct 27, 2026
- addedInput schema / properties / contact / description
```
Added value: +"email so a person can follow up"
```
- addedInput schema / properties / name / description
```
Added value: +"name as <area>.<function>, e.g. cad.gear or twin.bakery"
```
- addedInput schema / properties / url / description
```
Added value: +"where it lives: repo, MCP url, API docs"
```
- addedInput schema / properties / what / description
```
Added value: +"what it does, inputs and outputs"
```
Changed4 schema fields changedOct 26, 2026
- removedInput schema / properties / contact / description
```
Removed value: -"email so a person can follow up"
```
- removedInput schema / properties / name / description
```
Removed value: -"name as <area>.<function>, e.g. cad.gear or twin.bakery"
```
- removedInput schema / properties / url / description
```
Removed value: -"where it lives: repo, MCP url, API docs"
```
- removedInput schema / properties / what / description
```
Removed value: -"what it does, inputs and outputs"
```
Changed4 schema fields changedOct 26, 2026
- addedInput schema / properties / contact / description
```
Added value: +"email so a person can follow up"
```
- addedInput schema / properties / name / description
```
Added value: +"name as <area>.<function>, e.g. cad.gear or twin.bakery"
```
- addedInput schema / properties / url / description
```
Added value: +"where it lives: repo, MCP url, API docs"
```
- addedInput schema / properties / what / description
```
Added value: +"what it does, inputs and outputs"
```
Changed4 schema fields changedOct 26, 2026
- removedInput schema / properties / contact / properties
```
Removed value: -null
```
- removedInput schema / properties / name / properties
```
Removed value: -null
```
- removedInput schema / properties / url / properties
```
Removed value: -null
```
- removedInput schema / properties / what / properties
```
Removed value: -null
```
Changed8 schema fields changedOct 26, 2026
- removedInput schema / properties / contact / description
```
Removed value: -"email so a person can follow up"
```
- addedInput schema / properties / contact / properties
```
Added value: +null
```
- removedInput schema / properties / name / description
```
Removed value: -"name as <area>.<function>, e.g. cad.gear or twin.bakery"
```
- addedInput schema / properties / name / properties
```
Added value: +null
```
- removedInput schema / properties / url / description
```
Removed value: -"where it lives: repo, MCP url, API docs"
```
- addedInput schema / properties / url / properties
```
Added value: +null
```
- removedInput schema / properties / what / description
```
Removed value: -"what it does, inputs and outputs"
```
- addedInput schema / properties / what / properties
```
Added value: +null
```
First observedOct 17, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already mark this as a non-idempotent, open-world write that is not destructive. The description adds that submissions are intended for registry-wide use ('so every agent can use it'), but does not cover review, duplicates, permissions, or failure behavior; with annotation coverage, that is adequate but thin.

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

Conciseness5/5

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

A single front-loaded sentence with no wasted wording. The verb and scope appear immediately, and the outcome clause is brief.

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?

The tool has four parameters, two required, with 0% schema description coverage and no output schema. The description gives purpose only, not what each parameter should contain or what happens after proposal; annotations cover safety hints but not enough to make the definition complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents none of the four parameters, and the description does not explain name, what, url, or contact. It fails to compensate for 0% schema description coverage, leaving required fields (name, what) opaque.

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 ('Propose') and target ('ce-net registry'), and names the resource types (tool/twin/factory). It does not compare itself to siblings such as twin_submit or tools_search, so an agent must infer the boundaries.

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 conditions, prerequisites, or alternatives are given. The description only states the purpose; an agent gets no instruction on when to choose tool_add over twin_submit, factory_get, or tools_search.

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?