ProDisco
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| prodisco_searchToolsA | BROWSE API DOCUMENTATION. Find methods/types/functions by name from indexed TypeScript libraries. Use methodName to search (this searches indexed TypeScript typings only; it does NOT execute code or call external services). INDEXED: - @kubernetes/client-node: Kubernetes API client
FILTERS: library, documentType (method|type|function|script), category |
| prodisco_runSandboxA | PREREQUISITE: Call searchTools first to discover correct API methods and parameters. Do NOT guess - search to find available APIs before writing code. Execute TypeScript code in a sandboxed environment. IMPORTANT: When executing new code, ALWAYS provide a BEST PRACTICE: When writing complex logic, data transformations, or code you are uncertain about, use MODES: • execute (default): Blocking execution, waits for completion. Params: code OR cached (required), scriptName (required for caching), timeout. • stream: Real-time output streaming. Params: code OR cached (required), scriptName (required for caching), timeout. • async: Start execution and return immediately with execution ID. Params: code OR cached (required), scriptName (required for caching), timeout. • status: Get status of async execution. Params: executionId (required), wait (optional). • cancel: Cancel a running execution. Params: executionId (required). • list: List active/recent executions. Params: states (optional), limit (optional). • test: Run unit tests with structured results. Params: tests (required), code (optional implementation to test), timeout. CRITICAL: test() and assert are pre-injected globals - do NOT import them, do NOT call test.run(). Just write: test("name", () => { assert.is(actual, expected); }); Available assertions: assert.is(a,b), assert.ok(val), assert.equal(obj1,obj2), assert.not(val), assert.throws(fn). Sandbox provides console + process.env and restricts require() to an allowlist. ALLOWED IMPORTS:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| index.d.ts | TypeScript declaration file: index.d.ts |
| metadata.d.ts | TypeScript declaration file: metadata.d.ts |
| runSandbox.d.ts | TypeScript declaration file: runSandbox.d.ts |
| searchTools.d.ts | TypeScript declaration file: searchTools.d.ts |
TDQS
Scored across 2 tools
The two tools have entirely distinct purposes: one searches API documentation, the other executes code. No overlapping functionality.
Both tools follow a consistent verb_noun camelCase pattern (prodisco_runSandbox, prodisco_searchTools).
Two tools is minimal, but the server's scope is narrow (sandbox execution + API discovery). The runSandbox tool is complex with many modes, justifying a small set.
The sandbox execution covers all major modes (execute, stream, async, test) and the search tool is present. Minor gaps like script management are missing, but the core workflow is complete.