Skip to main content
Glama
tmustier

pi-code-mode-mcp

by tmustier
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Server Quality Checklist

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

  • Latest release: v0.4.0

  • Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion or overlap between tools. The agent can only use 'exec', making disambiguation trivial.

    Naming Consistency5/5

    With only one tool named 'exec', naming is perfectly consistent. The tool name is a straightforward verb, aligning with common conventions for action-oriented tools.

    Tool Count4/5

    The single tool 'exec' serves as a meta-orchestrator that can run arbitrary JavaScript to discover and compose other MCP tools. While unconventional, this design is intentional and scoped to its purpose. The count is minimal but arguably appropriate for a tool that replaces many specific ones.

    Completeness4/5

    The 'exec' tool provides a comprehensive environment to search, describe, and invoke any MCP tool, making it complete for its intended role as a discovery and composition layer. However, it lacks dedicated tools for specific operations, relying on programming logic, which may be considered a gap for agents that cannot write code.

  • Average 4.9/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
    • 12 commits in the last 12 weeks
    • Last stable release on
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • 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

  • Behavior5/5

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

    Annotations indicate destructiveHint=true and openWorldHint=true. The description details behavioral traits: not a security sandbox, has host authority over filesystem/network/process, console output captured, timeout/async behavior. Adds value beyond annotations.

    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 long but well-structured with bullet points for global APIs and sections on behavior. Every sentence adds value, though some repetition exists (e.g., search/describe guidance appears twice). Slightly verbose for the complexity, but effective.

    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 4 parameters with full schema coverage and no output schema, the description covers all necessary details: parameters, global APIs, execution context, output handling (CallToolResult vs text/JSON). No gaps for an agent to invoke correctly.

    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?

    Schema coverage is 100%. The description adds meaningful context: code must be a function body without JSON/Markdown fences, session_id defaults to 'default', timeout_ms defaults to server setting, max_output_chars is a limit with suggestion to filter large results in code. Enhances understanding beyond schema types.

    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 specifies the tool runs JavaScript to discover and compose upstream MCP tools. The verb 'Execute JavaScript' and resource 'MCP tools' are clear. It distinguishes itself as a meta-tool for dynamic composition, with no sibling tools to differentiate from.

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

    Usage Guidelines5/5

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

    Provides extensive guidance: 'Use search and describe when tool names or schemas are unknown; call known names directly.' Also warns against returning entire inventory and advises to union results from multiple search phrasings. Explicit alternatives are given for tool discovery.

    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

code-mode-mcp MCP server

Copy to your README.md:

Score Badge

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

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