Skip to main content
Glama

Change Model Size

change_model_size

Adjust the uniform scale of a 3D model by specifying a new size value to resize the entire object proportionally.

Instructions

Change the uniform size of the 3D model

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeYesNew size value (uniform scaling)

Implementation Reference

  • server.js:450-475 (registration)
    Complete tool registration for 'change_model_size' including schema definition and handler function. The tool accepts a positive 'size' parameter for uniform scaling, routes a 'changeSize' command to the browser session, and returns a confirmation message.
    // Register tool: change_model_size
    mcpServer.registerTool(
      'change_model_size',
      {
        title: 'Change Model Size',
        description: 'Change the uniform size of the 3D model',
        inputSchema: {
          size: z.number().positive().describe('New size value (uniform scaling)')
        }
      },
      async ({ size }) => {
        routeToCurrentSession({
          type: 'changeSize',
          size: size
        });
    
        return {
          content: [
            {
              type: 'text',
              text: `Model size changed to ${size}`
            }
          ]
        };
      }
    );
Behavior2/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. It states the action ('change') but doesn't explain what 'uniform size' means in practice, whether this is a destructive operation, what permissions are required, or how it affects the model state. This leaves significant gaps for a mutation tool.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, error conditions, or return values, and it fails to differentiate from sibling tools, leaving the agent with insufficient context for reliable use.

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?

The schema description coverage is 100%, with the 'size' parameter well-documented as 'New size value (uniform scaling)'. The description adds no additional parameter details beyond what the schema provides, so it meets the baseline of 3 for adequate but not enhanced semantic value.

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 verb ('change') and resource ('uniform size of the 3D model'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this from sibling tools like 'scale_model' or 'get_model_scale', which handle similar scaling operations, leaving some ambiguity about when to choose this tool over others.

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 versus alternatives such as 'scale_model' or 'get_model_scale'. It lacks context about prerequisites, typical scenarios, or exclusions, leaving the agent to infer usage from the tool name and schema alone.

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/aidenlab/hello3dmcp-server'

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