jungle-grid-mcp-server

Official

Overview Schema Related Servers Score Discussions(1)

estimate_job

Read-only

Estimate routing, capacity source, and expected cost for a proposed GPU workload to make informed decisions before submission.

Instructions

Estimate routing, capacity source, and expected cost for a proposed Jungle Grid workload without submitting it.

Input Schema

TableJSON Schema

Name	Required	Description
`workload`	Yes
`model_size`	No	Optional model size in GB.
`image`	No
`command`	No
`args`	No
`routing_mode`	No
`template`	No
`notes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed20 schema fields changedv0.1.9Jun 3, 2026

addedInput schema / properties / args

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / command
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / cost_priority

Removed value: -{
-  "enum": [
-    "low",
-    "balanced",
-    "high"
-  ],
-  "type": "string"
-}

removedInput schema / properties / disk_gb

Removed value: -{
-  "description": "Optional managed-provider local disk override in GB. Leave unset to let Jungle Grid auto-size from model_size_gb.",
-  "type": "number"
-}

removedInput schema / properties / gpu_class

Removed value: -{
-  "enum": [
-    "consumer",
-    "datacenter"
-  ],
-  "type": "string"
-}

removedInput schema / properties / gpu_type

Removed value: -{
-  "enum": [
-    "A100",
-    "A10G",
-    "H100",
-    "L4",
-    "RTX3090",
-    "RTX4090",
-    "RTX5090",
-    "T4"
-  ],
-  "type": "string"
-}

removedInput schema / properties / image / description
```
Removed value: -"Docker image to run."
```

removedInput schema / properties / latency_priority

Removed value: -{
-  "enum": [
-    "low",
-    "balanced",
-    "high"
-  ],
-  "type": "string"
-}

addedInput schema / properties / model_size

Added value: +{
+  "description": "Optional model size in GB.",
+  "type": "number"
+}

removedInput schema / properties / model_size_gb

Removed value: -{
-  "description": "Approximate model size in GB — drives tier selection.",
-  "type": "number"
-}

addedInput schema / properties / notes
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / optimize_for

Removed value: -{
-  "enum": [
-    "balanced",
-    "cost",
-    "speed"
-  ],
-  "type": "string"
-}

removedInput schema / properties / region_mode

Removed value: -{
-  "enum": [
-    "prefer",
-    "strict"
-  ],
-  "type": "string"
-}

removedInput schema / properties / region_preference
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / routing_mode

Added value: +{
+  "enum": [
+    "cost",
+    "speed",
+    "balanced"
+  ],
+  "type": "string"
+}

addedInput schema / properties / template
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / workload

Added value: +{
+  "enum": [
+    "inference",
+    "training",
+    "fine_tuning",
+    "batch"
+  ],
+  "type": "string"
+}

removedInput schema / properties / workload_type

Removed value: -{
-  "enum": [
-    "inference",
-    "training",
-    "fine-tuning",
-    "batch"
-  ],
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "workload_type",
-  "image"
-]New value: +[
+  "workload"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "properties": {
+        "available": {
+          "type": "boolean"
+        },
+        "can_submit": {
+          "type": "boolean"
+        },
+        "capacity": {
+          "additionalProperties": true,
+          "properties": {
+            "estimate_source": {
+              "type": "string"
+            },
+            "live_candidate_count": {
+              "type": "number"
+            },
+            "live_capacity_available": {
+              "type": "boolean"
+            },
+            "managed_capacity_available": {
+              "anyOf": [
+                {
+                  "type": "boolean"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "managed_profile_count": {
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "classification": {
+          "additionalProperties": true,
+          "properties": {
+            "acceleration_requirement": {
+              "type": "string"
+            },
+            "confidence": {
+              "type": "string"
+            },
+            "reasons": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "requires_gpu": {
+              "type": "boolean"
+            },
+            "workload_type": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "estimated_cost_max_usd": {
+          "type": "number"
+        },
+        "estimated_cost_min_usd": {
+          "type": "number"
+        },
+        "estimated_cost_usd": {
+          "additionalProperties": true,
+          "properties": {
+            "max": {
+              "type": "number"
+            },
+            "min": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "min",
+            "max"
+          ],
+          "type": "object"
+        },
+        "likely_gpu_type": {
+          "type": "string"
+        },
+        "routed_gpu_tier": {
+          "type": "string"
+        },
+        "routing": {
+          "additionalProperties": true,
+          "properties": {
+            "route_status": {
+              "type": "string"
+            },
+            "selected_accelerator": {
+              "type": "string"
+            },
+            "selected_route_source": {
+              "type": "string"
+            },
+            "selection_reason": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "screening": {}
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedv0.1.0May 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description need not reiterate safety. It adds value by specifying what the estimate covers (routing, capacity, cost). No contradictions with annotations. However, it omits details like rate limits or state effects, but these are less critical for a read-only estimate.

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?

The description is a single, well-structured sentence with no filler. It front-loads the key action and resource, making it easy to process. Every word contributes to understanding.

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?

Given 8 parameters (1 required) and an output schema, the description covers the tool's purpose but lacks parameter guidance. The complexity is moderate, and while the output schema reduces the need to explain return values, the missing parameter semantics leave the description incomplete for correct invocation.

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 13% (only model_size described). The tool description does not elaborate on how parameters like workload, routing_mode, image, command, etc., affect the estimate. With low coverage, the description should compensate but fails to add meaningful parameter context, leaving parameters ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Estimate'), the resource ('Jungle Grid workload'), and the specific aspects estimated ('routing, capacity source, expected cost'). It also distinguishes itself from submission tools by noting 'without submitting it', making the purpose very specific.

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?

The description implies when to use this tool (before submission) versus the sibling 'submit_job'. However, it does not explicitly exclude cases like checking existing jobs or provide alternative contexts. While clear for its primary use case, additional guidance on when not to use it would improve this dimension.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jungle-Grid/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server