Skip to main content
Glama

ai_modeling_symmetry_check

Read-only

Check image symmetry before P2 modeling using an uploaded file token or existing asset. Detect imbalance early to guide corrections and support reliable model preparation.

Instructions

Check image symmetry before P2 modelling using an uploaded file token or an existing image asset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ai_modeling_symmetry_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idNo
file_tokenNo
output_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only workflow placement; it says nothing about what the check returns (pass/fail, score, tolerance), whether the analysis is deterministic, or what happens when the image is not symmetric.

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?

A single front-loaded sentence with zero filler; the action and its inputs are stated immediately with no redundant restatement of the tool name.

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 read-only validation tool with no output schema and fully undocumented parameters, the description leaves key gaps: the shape of the symmetry result, the meaning of output_index, and whether the two inputs are mutually exclusive. An agent could call it, but could not interpret or select inputs confidently.

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?

With 0% schema description coverage the description must carry the load, and it does explain the two input routes (file token vs. existing image asset) and implies they are alternatives. However, the third parameter output_index (0-15) is never mentioned, and there is no clarification of precedence if both asset_id and file_token are supplied.

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?

States a specific verb and resource ('Check image symmetry') plus the workflow stage ('before P2 modelling'), which distinguishes it from generic sibling *_check tools like rig_check or canvas_run_check. It does not explicitly name an alternative, so it stops short of full differentiation.

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

Usage Guidelines3/5

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

The phrase 'before P2 modelling' implies when in the pipeline the tool belongs, and 'using an uploaded file token or an existing image asset' frames the two input routes. There is no explicit when-not guidance, no stated prerequisites, and no named alternative tool for related validation tasks.

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

Deploy Server

Other Tools