ce-net

code_call

Call a cell hosted in the sandbox: your own by name, or a community cell by cell (from...

Input Schema

Name	Required	Description	Default
`cell`	No
`name`	No
`input`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 29, 2026
- removedInput schema / properties / cell / description
```
Removed value: -"a community cell, e.g. hello.echo"
```
- removedInput schema / properties / input / description
```
Removed value: -"JSON value or string sent as one line"
```
- removedInput schema / properties / name / description
```
Removed value: -"your cell's name: 1-32 of a-z, 0-9, -"
```
Changed3 schema fields changedOct 28, 2026
- addedInput schema / properties / cell / description
```
Added value: +"a community cell, e.g. hello.echo"
```
- addedInput schema / properties / input / description
```
Added value: +"JSON value or string sent as one line"
```
- addedInput schema / properties / name / description
```
Added value: +"your cell's name: 1-32 of a-z, 0-9, -"
```
Changed3 schema fields changedOct 28, 2026
- removedInput schema / properties / cell / description
```
Removed value: -"a community cell, e.g. hello.echo"
```
- removedInput schema / properties / input / description
```
Removed value: -"JSON value or string sent as one line"
```
- removedInput schema / properties / name / description
```
Removed value: -"your cell's name: 1-32 of a-z, 0-9, -"
```
Changed3 schema fields changedOct 28, 2026
- addedInput schema / properties / cell / description
```
Added value: +"a community cell, e.g. hello.echo"
```
- addedInput schema / properties / input / description
```
Added value: +"JSON value or string sent as one line"
```
- addedInput schema / properties / name / description
```
Added value: +"your cell's name: 1-32 of a-z, 0-9, -"
```
Changed3 schema fields changedOct 27, 2026
- removedInput schema / properties / cell / description
```
Removed value: -"a community cell, e.g. hello.echo"
```
- removedInput schema / properties / input / description
```
Removed value: -"JSON value or string sent as one line"
```
- removedInput schema / properties / name / description
```
Removed value: -"your cell's name: 1-32 of a-z, 0-9, -"
```
Changed3 schema fields changedOct 27, 2026
- addedInput schema / properties / cell / description
```
Added value: +"a community cell, e.g. hello.echo"
```
- addedInput schema / properties / input / description
```
Added value: +"JSON value or string sent as one line"
```
- addedInput schema / properties / name / description
```
Added value: +"your cell's name: 1-32 of a-z, 0-9, -"
```
Changed3 schema fields changedOct 26, 2026
- removedInput schema / properties / cell / description
```
Removed value: -"a community cell, e.g. hello.echo"
```
- removedInput schema / properties / input / description
```
Removed value: -"JSON value or string sent as one line"
```
- removedInput schema / properties / name / description
```
Removed value: -"your cell's name: 1-32 of a-z, 0-9, -"
```
Changed3 schema fields changedOct 26, 2026
- addedInput schema / properties / cell / description
```
Added value: +"a community cell, e.g. hello.echo"
```
- addedInput schema / properties / input / description
```
Added value: +"JSON value or string sent as one line"
```
- addedInput schema / properties / name / description
```
Added value: +"your cell's name: 1-32 of a-z, 0-9, -"
```
Changed3 schema fields changedOct 26, 2026
- removedInput schema / properties / cell / properties
```
Removed value: -null
```
- removedInput schema / properties / input / properties
```
Removed value: -null
```
- removedInput schema / properties / name / properties
```
Removed value: -null
```
Changed6 schema fields changedOct 26, 2026
- removedInput schema / properties / cell / description
```
Removed value: -"a community cell, e.g. hello.echo"
```
- addedInput schema / properties / cell / properties
```
Added value: +null
```
- removedInput schema / properties / input / description
```
Removed value: -"JSON value or string sent as one line"
```
- addedInput schema / properties / input / properties
```
Added value: +null
```
- removedInput schema / properties / name / description
```
Removed value: -"your cell's name: 1-32 of a-z, 0-9, -"
```
- addedInput schema / properties / name / properties
```
Added value: +null
```

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / cell

Added value: +{
+  "description": "a community cell, e.g. hello.echo",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "name"
-]
```

AddedOct 23, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is covered structurally. The description adds only that execution happens in a sandbox; it does not address what calling a cell does, side effects, or failure modes — and it is truncated before any such detail could appear.

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

Conciseness3/5

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

What exists is compact and front-loads the key distinction, but the text is literally truncated mid-parenthetical, which is a structural defect rather than conciseness.

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 3-parameter, zero-coverage, no-output-schema tool with open-world behavior, the description should explain the `input` payload shape, what a cell invocation returns, and how it differs from `cell_call`. The truncated one-liner delivers none of this.

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

Parameters3/5

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

Schema description coverage is 0%, so the description carries the burden. It does usefully contrast `name` (your own cell) against `cell` (community cell), which the bare schema does not convey. But the `input` parameter — presumably the argument payload — is never mentioned, and the sentence is incomplete.

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 verb+resource is specific ("Call a cell hosted in the sandbox"), and it hints at two modes of addressing a cell. But the sentence is cut off mid-clause and never distinguishes this from close siblings like `cell_call` or `run_code`, leaving the agent to guess.

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

Usage Guidelines3/5

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

It implicitly gives a routing rule — use `name` for your own cell, `cell` for a community cell — which is real usage guidance. However the explanation trails off at "(from...", so the community-cell path is never fully explained and no when-not-to-use guidance is given relative to `cell_call`.

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?