Skip to main content
Glama
elusznik

MCP Server Code Execution Mode

by elusznik
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.3.0

  • Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'run_python' has a clearly defined and distinct purpose for executing Python code in a sandboxed environment.

    Naming Consistency5/5

    The naming follows a consistent verb_noun pattern with 'run_python', and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.

    Tool Count2/5

    A single tool is too few for a server named 'MCP Server Code Execution Mode', which suggests a broader scope for code execution. While the tool is powerful, the set feels thin and limited, lacking coverage for other potential operations like managing sessions or handling different languages.

    Completeness2/5

    The tool set is severely incomplete for a code execution server. It only supports Python execution, missing obvious gaps such as tools for other programming languages, session management, code inspection, or error handling, which are essential for a comprehensive code execution environment.

  • Average 4.1/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under GPL 3.0.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior4/5

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

    With no annotations provided, the description carries the full burden of behavioral disclosure and does so effectively. It describes key behavioral traits: stateful/persistent execution environment, sandboxed nature, preservation of variables/functions/imports across calls, and support for loading MCP servers. It doesn't mention rate limits, authentication needs, or error handling, but provides substantial operational context beyond basic functionality.

    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 appropriately sized and front-loaded with the core purpose in the first sentence. Each subsequent sentence adds valuable information about persistence, usage scenarios, and MCP server support. There's minimal redundancy, though the final sentence about MCP servers could be integrated more smoothly with the preceding content.

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

    Completeness4/5

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

    Given the tool's complexity (stateful code execution with persistence) and lack of annotations/output schema, the description provides substantial context about the execution environment, persistence model, and MCP server integration. It doesn't describe return values or error formats, but covers the operational model well. For a tool with this complexity and no structured behavioral annotations, it's quite comprehensive.

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

    Parameters3/5

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

    Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description mentions the 'servers' array parameter but doesn't add significant semantic meaning beyond what's in the schema descriptions. It provides context about MCP server availability but doesn't enhance understanding of parameter usage beyond the comprehensive schema documentation.

    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 tool's purpose with specific verbs ('executes Python code') and resources ('stateful, persistent rootless sandbox environment similar to a Jupyter notebook'). It distinguishes the tool's unique capabilities by mentioning variable persistence across calls and MCP server loading, which would differentiate it from any hypothetical siblings. The description goes beyond just restating the name to explain the execution environment.

    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 explicit guidance on when to use this tool ('for general code execution, data analysis, or when the user asks to run code'), which gives clear context for its application. However, since there are no sibling tools mentioned, it cannot provide guidance on when to use alternatives. The guidance is comprehensive within the given context but lacks sibling differentiation.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

mcp-server-code-execution-mode MCP server

Copy to your README.md:

Score Badge

mcp-server-code-execution-mode MCP server

Copy to your README.md:

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/elusznik/mcp-server-code-execution-mode'

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