Skip to main content
Glama

translate_muiscan

Transform muiscan JSON data into production-ready MUI web components for design-to-code workflows.

Instructions

Transform muiscan JSON to web components

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonYesThe muiscan JSON to transform

Implementation Reference

  • server.js:72-84 (handler)
    The handler function for the 'translate_muiscan' tool. It extracts the 'json' argument from the request, passes it to transformNode, and returns the output as text content.
    if (request.params.name === "translate_muiscan") {
      const json = request.params.arguments.json;
      const output = transformNode(json);
    
      return {
        content: [
          {
            type: "text",
            text: output,
          },
        ],
      };
    }
  • The schema definition for the 'translate_muiscan' tool, including name, description, and input schema requiring a 'json' string.
    {
      name: "translate_muiscan",
      description: "Transform muiscan JSON to web components",
      inputSchema: {
        type: "object",
        properties: {
          json: {
            type: "string",
            description: "The muiscan JSON to transform",
          },
        },
        required: ["json"],
      },
    },
  • server.js:49-68 (registration)
    Registration of the 'translate_muiscan' tool in the ListToolsRequestHandler, making it discoverable by clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "translate_muiscan",
            description: "Transform muiscan JSON to web components",
            inputSchema: {
              type: "object",
              properties: {
                json: {
                  type: "string",
                  description: "The muiscan JSON to transform",
                },
              },
              required: ["json"],
            },
          },
        ],
      };
    });
  • The transformNode helper function called by the handler. Currently a stub that echoes the input, with comments indicating intended use with MCP prompt for transformation.
    function transformNode(input) {
      // Here, 'input' is whatever text / muiscan snippet you paste in
      // The MCP uses your prompt to generate the proper <mui-*> output
    
      // For now, we just return the input directly,
      // because your MCP prompt contains all the rules
      return input;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Transform' but doesn't disclose behavioral traits like whether it's read-only, destructive, requires authentication, or has rate limits. This leaves significant gaps in understanding the tool's behavior.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero waste, clearly front-loading the purpose. It's appropriately sized for a simple tool, making it easy to parse without unnecessary details.

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

Completeness2/5

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

Given no annotations, no output schema, and a transformation tool, the description is incomplete. It lacks details on what the transformation entails, the format of web components produced, error handling, or any behavioral context, making it inadequate for full understanding.

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 the 'json' parameter fully. The description adds no additional meaning beyond implying the input is muiscan JSON, which aligns with the schema. Baseline 3 is appropriate as the schema handles parameter documentation.

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

Purpose4/5

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

The description clearly states the action ('Transform') and the resource ('muiscan JSON to web components'), making the purpose understandable. However, it doesn't differentiate from siblings (none exist) or specify what 'muiscan JSON' is, which slightly limits specificity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool, such as prerequisites, alternatives, or context. With no siblings, it's the only option, but it lacks any usage instructions or exclusions, leaving the agent without operational context.

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/michaeltrilford/muiscan-mcp'

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