ce-net

request

Ask the ce-net factories for a part, a print run, a design or a build.

Input Schema

Name	Required	Description	Default
`name`	No
`what`	Yes
`when`	No
`where`	No
`budget`	No
`contact`	No
`callback_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
Changed6 schema fields changedOct 29, 2026
- removedInput schema / properties / budget / description
```
Removed value: -"budget, with currency"
```
- removedInput schema / properties / contact / description
```
Removed value: -"email or phone so a person can follow up"
```
- removedInput schema / properties / name / description
```
Removed value: -"your name or company"
```
- removedInput schema / properties / what / description
```
Removed value: -"what you need, in plain words (part, quantity, material, purpose)"
```
- removedInput schema / properties / when / description
```
Removed value: -"when you need it"
```
- removedInput schema / properties / where / description
```
Removed value: -"where it should end up (city, country)"
```
Changed6 schema fields changedOct 28, 2026
- addedInput schema / properties / budget / description
```
Added value: +"budget, with currency"
```
- addedInput schema / properties / contact / description
```
Added value: +"email or phone so a person can follow up"
```
- addedInput schema / properties / name / description
```
Added value: +"your name or company"
```
- addedInput schema / properties / what / description
```
Added value: +"what you need, in plain words (part, quantity, material, purpose)"
```
- addedInput schema / properties / when / description
```
Added value: +"when you need it"
```
- addedInput schema / properties / where / description
```
Added value: +"where it should end up (city, country)"
```
Changed6 schema fields changedOct 28, 2026
- removedInput schema / properties / budget / description
```
Removed value: -"budget, with currency"
```
- removedInput schema / properties / contact / description
```
Removed value: -"email or phone so a person can follow up"
```
- removedInput schema / properties / name / description
```
Removed value: -"your name or company"
```
- removedInput schema / properties / what / description
```
Removed value: -"what you need, in plain words (part, quantity, material, purpose)"
```
- removedInput schema / properties / when / description
```
Removed value: -"when you need it"
```
- removedInput schema / properties / where / description
```
Removed value: -"where it should end up (city, country)"
```
Changed6 schema fields changedOct 28, 2026
- addedInput schema / properties / budget / description
```
Added value: +"budget, with currency"
```
- addedInput schema / properties / contact / description
```
Added value: +"email or phone so a person can follow up"
```
- addedInput schema / properties / name / description
```
Added value: +"your name or company"
```
- addedInput schema / properties / what / description
```
Added value: +"what you need, in plain words (part, quantity, material, purpose)"
```
- addedInput schema / properties / when / description
```
Added value: +"when you need it"
```
- addedInput schema / properties / where / description
```
Added value: +"where it should end up (city, country)"
```
Changed6 schema fields changedOct 27, 2026
- removedInput schema / properties / budget / description
```
Removed value: -"budget, with currency"
```
- removedInput schema / properties / contact / description
```
Removed value: -"email or phone so a person can follow up"
```
- removedInput schema / properties / name / description
```
Removed value: -"your name or company"
```
- removedInput schema / properties / what / description
```
Removed value: -"what you need, in plain words (part, quantity, material, purpose)"
```
- removedInput schema / properties / when / description
```
Removed value: -"when you need it"
```
- removedInput schema / properties / where / description
```
Removed value: -"where it should end up (city, country)"
```
Changed6 schema fields changedOct 27, 2026
- addedInput schema / properties / budget / description
```
Added value: +"budget, with currency"
```
- addedInput schema / properties / contact / description
```
Added value: +"email or phone so a person can follow up"
```
- addedInput schema / properties / name / description
```
Added value: +"your name or company"
```
- addedInput schema / properties / what / description
```
Added value: +"what you need, in plain words (part, quantity, material, purpose)"
```
- addedInput schema / properties / when / description
```
Added value: +"when you need it"
```
- addedInput schema / properties / where / description
```
Added value: +"where it should end up (city, country)"
```
Changed6 schema fields changedOct 26, 2026
- removedInput schema / properties / budget / description
```
Removed value: -"budget, with currency"
```
- removedInput schema / properties / contact / description
```
Removed value: -"email or phone so a person can follow up"
```
- removedInput schema / properties / name / description
```
Removed value: -"your name or company"
```
- removedInput schema / properties / what / description
```
Removed value: -"what you need, in plain words (part, quantity, material, purpose)"
```
- removedInput schema / properties / when / description
```
Removed value: -"when you need it"
```
- removedInput schema / properties / where / description
```
Removed value: -"where it should end up (city, country)"
```
Changed6 schema fields changedOct 26, 2026
- addedInput schema / properties / budget / description
```
Added value: +"budget, with currency"
```
- addedInput schema / properties / contact / description
```
Added value: +"email or phone so a person can follow up"
```
- addedInput schema / properties / name / description
```
Added value: +"your name or company"
```
- addedInput schema / properties / what / description
```
Added value: +"what you need, in plain words (part, quantity, material, purpose)"
```
- addedInput schema / properties / when / description
```
Added value: +"when you need it"
```
- addedInput schema / properties / where / description
```
Added value: +"where it should end up (city, country)"
```
Changed6 schema fields changedOct 26, 2026
- removedInput schema / properties / budget / properties
```
Removed value: -null
```
- removedInput schema / properties / contact / properties
```
Removed value: -null
```
- removedInput schema / properties / name / properties
```
Removed value: -null
```
- removedInput schema / properties / what / properties
```
Removed value: -null
```
- removedInput schema / properties / when / properties
```
Removed value: -null
```
- removedInput schema / properties / where / properties
```
Removed value: -null
```
Changed12 schema fields changedOct 26, 2026
- removedInput schema / properties / budget / description
```
Removed value: -"budget, with currency"
```
- addedInput schema / properties / budget / properties
```
Added value: +null
```
- removedInput schema / properties / contact / description
```
Removed value: -"email or phone so a person can follow up"
```
- addedInput schema / properties / contact / properties
```
Added value: +null
```
- removedInput schema / properties / name / description
```
Removed value: -"your name or company"
```
- addedInput schema / properties / name / properties
```
Added value: +null
```
- removedInput schema / properties / what / description
```
Removed value: -"what you need, in plain words (part, quantity, material, purpose)"
```
- addedInput schema / properties / what / properties
```
Added value: +null
```
- removedInput schema / properties / when / description
```
Removed value: -"when you need it"
```
- addedInput schema / properties / when / properties
```
Added value: +null
```
- removedInput schema / properties / where / description
```
Removed value: -"where it should end up (city, country)"
```
- addedInput schema / properties / where / properties
```
Added value: +null
```
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 declare this as a non-read-only, non-idempotent, open-world operation. The description adds only the categories of things that can be requested and says nothing about duplicate submission risk from non-idempotency, what happens after submission, whether external factories are involved, or expected response behavior.

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?

A single front-loaded sentence with no filler. It is efficient, though the lack of any follow-up structure for parameters or workflow keeps it from being a 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?

For a 7-parameter open-world mutation tool with no output schema, the description is far too thin. It omits what the tool returns (e.g., a request ID), how to track the request afterward, and what the remaining optional parameters do.

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 burden of explaining 7 parameters. It only hints at the required 'what' field via examples (part, print run, design, build); name, when, where, budget, contact, and callback_url are entirely undocumented in both schema and description.

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?

It states a clear verb and object: asking ce-net factories for a part, print run, design, or build. The request categories are specific enough for an agent to grasp the intent, but it never distinguishes itself from siblings like request_reply, request_status, or factories_search.

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 guidance on when to use this tool versus request_reply, request_status, compute_submit, print_plate_quote, or source_request. Prerequisites, timing, and post-submission workflow are entirely left 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?