Skip to main content
Glama
Sign In

Cloud World Model

by ai.cloudworldmodel
OverviewDiscussionsAdmin

Inject Traffic

simulation.inject_traffic

Requires simulationId from simulation.create and target traffic RPS. Returns applied traffic settings. Next tool is simulation.step, then simulation.metrics to read observed latency; do not assume its direction. No API key required; demo limits apply. Read resource cwm://guides/public/simulation.inject_traffic

Input Schema

NameRequiredDescriptionDefault
rampNo
randomNo
targetRpsNo
deltaPercentNo
simulationIdNoID returned by simulation.create.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / simulationId / description
      Added value: +"ID returned by simulation.create."
  2. Changed11 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / deltaPercent / description
      Removed value: -"Relative traffic change; must be greater than -100."
    • removedInput schema / properties / deltaPercent / exclusiveMinimum
      Removed value: --100
    • changedInput schema / properties / ramp / additionalProperties
      Previous value: -falseNew value: +true
    • removedInput schema / properties / ramp / description
      Removed value: -"Schedule a ramp from startRps to endRps over durationSteps; mutually exclusive with other selectors."
    • removedInput schema / properties / ramp / properties
      Removed value: -{
-  "durationSteps": {
-    "maximum": 500,
-    "minimum": 1,
-    "type": "integer"
-  },
-  "endRps": {
-    "maximum": 500000,
-    "minimum": 0,
-    "type": "integer"
-  },
-  "startRps": {
-    "maximum": 500000,
-    "minimum": 0,
-    "type": "integer"
-  }
-}
    • removedInput schema / properties / ramp / required
      Removed value: -[
-  "startRps",
-  "endRps",
-  "durationSteps"
-]
    • removedInput schema / properties / random / description
      Removed value: -"Explicitly select a random stress spike; never selected implicitly."
    • removedInput schema / properties / simulationId / description
      Removed value: -"Simulation ID returned by simulation.create. Preserve Mcp-Session-Id to omit this field and use the session's current simulation; if your connector starts a fresh MCP session for each call (for example Grok Bot or Cursor), pass this explicit ID after every fresh initialization. A fresh session has no current-simulation pointer and returns NO_ACTIVE_SIMULATION when the ID is omitted. Anonymous capabilities are short-lived (30 minutes by default), unguessable, and revoked when the demo expires or is deleted; proxy IP changes do not invalidate them. Do not treat the ID as a durable share link."
    • removedInput schema / properties / targetRps / description
      Removed value: -"Absolute traffic level in RPS to set. Server-capped at 10000 RPS in demo mode."
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": true,
-  "properties": {
-    "id": {
-      "description": "Simulation ID",
-      "type": "string"
-    },
-    "status": {
-      "description": "Updated simulation status",
-      "type": "string"
-    },
-    "traffic": {
-      "description": "New traffic level in RPS after injection",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • addedInput schema / properties / ramp
      Added value: +{
+  "additionalProperties": false,
+  "description": "Schedule a ramp from startRps to endRps over durationSteps; mutually exclusive with other selectors.",
+  "properties": {
+    "durationSteps": {
+      "maximum": 500,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "endRps": {
+      "maximum": 500000,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "startRps": {
+      "maximum": 500000,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "startRps",
+    "endRps",
+    "durationSteps"
+  ],
+  "type": "object"
+}
  4. Changed4 schema fields changed
    • addedInput schema / properties / deltaPercent
      Added value: +{
+  "description": "Relative traffic change; must be greater than -100.",
+  "exclusiveMinimum": -100,
+  "type": "number"
+}
    • addedInput schema / properties / random
      Added value: +{
+  "const": true,
+  "description": "Explicitly select a random stress spike; never selected implicitly.",
+  "type": "boolean"
+}
    • addedInput schema / properties / targetRps
      Added value: +{
+  "description": "Absolute traffic level in RPS to set. Server-capped at 10000 RPS in demo mode.",
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / traffic
      Removed value: -{
-  "description": "Absolute traffic level in RPS to set. Omit to trigger a random spike instead. Server-capped at 10000 RPS in demo mode.",
-  "type": "number"
-}
  5. Changed1 schema field changed
    • changedInput schema / properties / simulationId / description
      Previous value: -"Simulation ID returned by simulation.create. Preserve Mcp-Session-Id to omit this field and use the session's current simulation; if your connector starts a fresh MCP session for each call (for example Grok Bot or Cursor), pass this explicit ID. A fresh session has no current-simulation pointer and returns NO_ACTIVE_SIMULATION when the ID is omitted. Anonymous capabilities are short-lived, bound to the creating anonymous client, and revoked when the demo expires or is deleted; do not treat the ID as a durable share link."New value: +"Simulation ID returned by simulation.create. Preserve Mcp-Session-Id to omit this field and use the session's current simulation; if your connector starts a fresh MCP session for each call (for example Grok Bot or Cursor), pass this explicit ID after every fresh initialization. A fresh session has no current-simulation pointer and returns NO_ACTIVE_SIMULATION when the ID is omitted. Anonymous capabilities are short-lived (30 minutes by default), unguessable, and revoked when the demo expires or is deleted; proxy IP changes do not invalidate them. Do not treat the ID as a durable share link."
  6. Changed1 schema field changed
    • changedInput schema / properties / simulationId / description
      Previous value: -"Simulation ID returned by simulation.create. Optional in demo sessions — omit to target this session's current simulation (set by simulation.create and updated by the most recent successful explicit use). If the session has no current simulation you get a NO_ACTIVE_SIMULATION result."New value: +"Simulation ID returned by simulation.create. Preserve Mcp-Session-Id to omit this field and use the session's current simulation; if your connector starts a fresh MCP session for each call (for example Grok Bot or Cursor), pass this explicit ID. A fresh session has no current-simulation pointer and returns NO_ACTIVE_SIMULATION when the ID is omitted. Anonymous capabilities are short-lived, bound to the creating anonymous client, and revoked when the demo expires or is deleted; do not treat the ID as a durable share link."
  7. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "One-sentence goal for this session — e.g. 'train RL agent on AWS', 'compare GCP vs Azure costs', or 'run chaos test on database tier'.",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "context"
-]
  8. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare a mutating but non-destructive, non-idempotent, closed-world operation; the description adds real extra context: no API key needed, demo limits apply, and the response contains the applied traffic settings. The warning 'do not assume its direction' about latency is genuinely useful but cryptic and unexplained.

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?

Requirements are front-loaded and there is little padding, but the telegraphic style packs five unrelated ideas into run-on clauses and the latency-direction warning arrives without context. Some sentences (the resource pointer to cwm://guides/...) would work better as a trailing reference than inline prose.

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

Completeness3/5

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

No output schema exists, and the description compensates by stating the return value is the applied traffic settings, plus it establishes the workflow position. However, for a tool with a nested free-form 'ramp' object and three unexplained parameters, the definition leaves too much of the call contract unstated.

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 only 20%, so the description must carry the parameter burden, yet it only explains simulationId's provenance and targetRps as RPS. 'ramp' (a free-form nested object), 'random' (a const-true boolean), and 'deltaPercent' receive no explanation at all. It also asserts simulationId and target RPS are 'required' while the schema marks zero required properties, leaving the agent unsure which inputs are mandatory.

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+resource ('inject traffic') and names the inputs that drive it (simulationId, target RPS), which separates it from the failure-injection sibling. It never explicitly contrasts itself with simulation.inject_failure, so sibling differentiation is only implicit.

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

Usage Guidelines4/5

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

Gives a clear prerequisite (simulationId must come from simulation.create) and an explicit follow-on sequence (simulation.step, then simulation.metrics). It does not say when to prefer this over simulation.inject_failure or what to do if injection is rejected by demo limits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cloud World Model 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