Skip to main content
Glama
jmpijll

unraid-code-mode-mcp

by jmpijll
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Search Unraid GraphQL schema

search

Discover Unraid GraphQL operations by writing JavaScript code against the schema index.

Instructions

Search the Unraid GraphQL schema by writing JavaScript.

The sandbox is read-only — no network. Use this tool to discover what to call before invoking execute.

Globals

  • index — { namespace, title, version, sourceUrl, operations[], types }. Each operation is the compact form: { kind: 'query'|'mutation', namespace: 'local', name, description, args, returnType, returnTypeFields, deprecated }.

  • unraid.local — same shape as index for parity with the execute tool. May be null if no spec is loaded.

  • searchOperations(query, limit?) — text-ranked search across name, description, args, and return type.

  • getOperation(name) — full operation info including arg types and return-type field hints.

  • findOperationsByName(substring) — list operations whose name contains the substring (case-insensitive).

  • getType(typeName) — full named-type info (fields for OBJECT/INTERFACE/INPUT_OBJECT, members for UNION, enumValues for ENUM).

  • console.log() — captured into the tool output.

Examples

// All queries that mention "docker"
searchOperations('docker', 20).map(function (op) { return op.name; });
// Full detail on the `info` query
getOperation('info');
// Inspect the Array type to see its fields
getType('Array');

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesJavaScript code to execute against the operation index. The final expression is returned.

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It explicitly states the sandbox is read-only and has no network, which are critical traits. It also describes the sandbox environment, available globals, and that console.log output is captured. This provides sufficient transparency, though it could mention response format or error 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?

The description is well-structured with sections for globals, functions, and examples. Every sentence adds value. However, it is somewhat verbose; the examples and function lists could be slightly condensed without losing clarity. Still, the structure aids comprehension.

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

Completeness5/5

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

Given the tool's complexity (JavaScript execution in a sandbox with multiple globals and no output schema), the description is remarkably complete. It covers the environment, all available functions with their purpose, input/output shapes, and concrete examples. An agent could immediately use the tool correctly based on this description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter 'code' with a minimal description. The tool's description compensates extensively by detailing the global functions and variables available (e.g., searchOperations, getOperation, getType), their signatures, and usage examples. This adds immense meaning beyond the schema, effectively teaching the agent how to construct the JavaScript code.

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 'Search the Unraid GraphQL schema by writing JavaScript.' It specifies the resource and action, and distinguishes from sibling 'execute' by positioning this as a discovery tool before invocation. The verb 'search' and resource 'Unraid GraphQL schema' are specific and unambiguous.

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 provides clear context: use this tool to discover what to call before invoking 'execute', and notes the sandbox is read-only with no network. It does not explicitly state when not to use it, but the sibling relationship and discovery purpose imply that. The examples further guide usage, making it nearly complete.

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

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/jmpijll/unraid-code-mode-mcp'

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