Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

cell_call

Destructive

Call one op of a cell (see cells_find), JSON in and JSON out.

Input Schema

NameRequiredDescriptionDefault
opYes
capNo
argsNo
cellYes
deviceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / args / description
      Removed value: -"the request as JSON; leave out for an op that takes nothing"
    • addedInput schema / properties / cap
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / cell / description
      Removed value: -"the cell's name, e.g. printer.pair"
    • removedInput schema / properties / device / description
      Removed value: -"your device's name from my_devices, or the start of its node key"
    • removedInput schema / properties / op / description
      Removed value: -"the op's name, e.g. List"
    • changedInput schema / required
      Previous value: -[
-  "cell",
-  "op",
-  "device"
-]New value: +[
+  "cell",
+  "op"
+]
  2. Changed6 schema fields changed
    • addedInput schema / properties / args / description
      Added value: +"the request as JSON; leave out for an op that takes nothing"
    • removedInput schema / properties / cap
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / cell / description
      Added value: +"the cell's name, e.g. printer.pair"
    • addedInput schema / properties / device / description
      Added value: +"your device's name from my_devices, or the start of its node key"
    • addedInput schema / properties / op / description
      Added value: +"the op's name, e.g. List"
    • changedInput schema / required
      Previous value: -[
-  "cell",
-  "op"
-]New value: +[
+  "cell",
+  "op",
+  "device"
+]
  3. Changed6 schema fields changed
    • removedInput schema / properties / args / description
      Removed value: -"the request as JSON; leave out for an op that takes nothing"
    • addedInput schema / properties / cap
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / cell / description
      Removed value: -"the cell's name, e.g. printer.pair"
    • removedInput schema / properties / device / description
      Removed value: -"your device's name from my_devices, or the start of its node key"
    • removedInput schema / properties / op / description
      Removed value: -"the op's name, e.g. List"
    • changedInput schema / required
      Previous value: -[
-  "cell",
-  "op",
-  "device"
-]New value: +[
+  "cell",
+  "op"
+]
  4. Changed6 schema fields changed
    • addedInput schema / properties / args / description
      Added value: +"the request as JSON; leave out for an op that takes nothing"
    • removedInput schema / properties / cap
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / cell / description
      Added value: +"the cell's name, e.g. printer.pair"
    • addedInput schema / properties / device / description
      Added value: +"your device's name from my_devices, or the start of its node key"
    • addedInput schema / properties / op / description
      Added value: +"the op's name, e.g. List"
    • changedInput schema / required
      Previous value: -[
-  "cell",
-  "op"
-]New value: +[
+  "cell",
+  "op",
+  "device"
+]
  5. Changed6 schema fields changed
    • removedInput schema / properties / args / description
      Removed value: -"the request as JSON; leave out for an op that takes nothing"
    • addedInput schema / properties / cap
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / cell / description
      Removed value: -"the cell's name, e.g. printer.pair"
    • removedInput schema / properties / device / description
      Removed value: -"your device's name from my_devices, or the start of its node key"
    • removedInput schema / properties / op / description
      Removed value: -"the op's name, e.g. List"
    • changedInput schema / required
      Previous value: -[
-  "cell",
-  "op",
-  "device"
-]New value: +[
+  "cell",
+  "op"
+]
  6. Changed6 schema fields changed
    • addedInput schema / properties / args / description
      Added value: +"the request as JSON; leave out for an op that takes nothing"
    • removedInput schema / properties / cap
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / cell / description
      Added value: +"the cell's name, e.g. printer.pair"
    • addedInput schema / properties / device / description
      Added value: +"your device's name from my_devices, or the start of its node key"
    • addedInput schema / properties / op / description
      Added value: +"the op's name, e.g. List"
    • changedInput schema / required
      Previous value: -[
-  "cell",
-  "op"
-]New value: +[
+  "cell",
+  "op",
+  "device"
+]
  7. Changed6 schema fields changed
    • removedInput schema / properties / args / description
      Removed value: -"the request as JSON; leave out for an op that takes nothing"
    • addedInput schema / properties / cap
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / cell / description
      Removed value: -"the cell's name, e.g. printer.pair"
    • removedInput schema / properties / device / description
      Removed value: -"your device's name from my_devices, or the start of its node key"
    • removedInput schema / properties / op / description
      Removed value: -"the op's name, e.g. List"
    • changedInput schema / required
      Previous value: -[
-  "cell",
-  "op",
-  "device"
-]New value: +[
+  "cell",
+  "op"
+]
  8. Changed4 schema fields changed
    • addedInput schema / properties / args / description
      Added value: +"the request as JSON; leave out for an op that takes nothing"
    • addedInput schema / properties / cell / description
      Added value: +"the cell's name, e.g. printer.pair"
    • addedInput schema / properties / device / description
      Added value: +"your device's name from my_devices, or the start of its node key"
    • addedInput schema / properties / op / description
      Added value: +"the op's name, e.g. List"
  9. Changed4 schema fields changed
    • removedInput schema / properties / args / properties
      Removed value: -null
    • removedInput schema / properties / cell / properties
      Removed value: -null
    • removedInput schema / properties / device / properties
      Removed value: -null
    • removedInput schema / properties / op / properties
      Removed value: -null
  10. Changed8 schema fields changed
    • removedInput schema / properties / args / description
      Removed value: -"the request as JSON; leave out for an op that takes nothing"
    • addedInput schema / properties / args / properties
      Added value: +null
    • removedInput schema / properties / cell / description
      Removed value: -"the cell's name, e.g. printer.pair"
    • addedInput schema / properties / cell / properties
      Added value: +null
    • removedInput schema / properties / device / description
      Removed value: -"your device's name from my_devices, or the start of its node key"
    • addedInput schema / properties / device / properties
      Added value: +null
    • removedInput schema / properties / op / description
      Removed value: -"the op's name, e.g. List"
    • addedInput schema / properties / op / properties
      Added value: +null
  11. Added

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, lowering the description's burden. The description adds only 'JSON in and JSON out' and does not clarify what side effects occur, whether authorization is required, or how destructive calls behave.

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?

The description is short and front-loaded, but it is under-specified rather than efficiently concise. The parenthetical cells_find pointer is useful, while 'JSON in and JSON out' is only marginally informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, open-world, non-idempotent generic call tool with five undocumented parameters and no output schema. The description does not provide enough information for an agent to safely construct a call or understand its consequences.

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?

Schema description coverage is 0% for all five parameters, and the description mentions none of them directly. It does not explain the required cell and op parameters or the optional cap, args, and device fields, leaving the agent with no semantic guidance beyond the schema's bare names.

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 gives a verb-resource pair ('Call one op of a cell') and points to cells_find for discovery, so the basic action is identifiable. However, 'op' is undefined, and it does not distinguish this tool from siblings such as code_call, integration_call, or collab_op.

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?

The only usage cue is '(see cells_find)', which helps with finding a cell but says nothing about when this tool should be used versus code_call or integration_call. There are no prerequisites, exclusions, or failure conditions.

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