Skip to main content
Glama

run_code

Execute Sonic Pi code to generate music and control audio synthesis programmatically through the MCP server interface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesSonic Pi code to execute

Implementation Reference

  • The asynchronous handler function for the 'run_code' tool. It sends the provided Sonic Pi code to the OSC client and returns a success response or throws an error on failure.
    async ({ code }: RunCodeParams) => {
      try {
        this.oscClient.send('/run-code', code);
        return {
          content: [{ 
            type: "text", 
            text: "Code executed successfully" 
          }]
        };
      } catch (error) {
        console.error('Error in run_code:', error);
        throw new Error('Failed to execute code');
      }
    }
  • Zod input schema for the 'run_code' tool, defining a required 'code' string parameter.
    {
      code: z.string().describe("Sonic Pi code to execute")
    },
  • TypeScript interface defining the parameters for the 'run_code' handler function.
    interface RunCodeParams {
      code: string;
    }
  • src/server.ts:72-91 (registration)
    Registration of the 'run_code' tool on the MCP server using server.tool(), specifying name, input schema, and handler function.
    this.server.tool(
      "run_code",
      {
        code: z.string().describe("Sonic Pi code to execute")
      },
      async ({ code }: RunCodeParams) => {
        try {
          this.oscClient.send('/run-code', code);
          return {
            content: [{ 
              type: "text", 
              text: "Code executed successfully" 
            }]
          };
        } catch (error) {
          console.error('Error in run_code:', error);
          throw new Error('Failed to execute code');
        }
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/abhishekjairath/sonic-pi-mcp'

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