Skip to main content
Glama
liangjunglj-cpu

Almond MCP

place_diagram_asset

Place an indexed diagram asset (SVG, DWG, DXF) at any location with adjustable rotation and scale for architectural design.

Instructions

Places an indexed diagram asset (SVG, DWG, DXF).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
zNo
scaleNo
asset_idYes
rotation_degreesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
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. It states the tool 'places' an asset but does not disclose side effects (e.g., overwriting, coordinate system, success/failure behavior) or permissions needed.

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

Conciseness3/5

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

The description is a single short sentence, which is concise but lacks necessary detail. It is front-loaded but sacrifices completeness.

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 the tool has 6 parameters and no annotations, the description is inadequate. It does not mention the return value or output schema, leaving the agent uncertain about what happens after placement.

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?

The input schema has 6 parameters with 0% description coverage. The description adds no meaning to the parameters; it only mentions the asset type but does not explain 'x', 'y', 'z', 'scale', 'rotation_degrees', or the required 'asset_id'.

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 specifies the verb 'places' and the resource 'indexed diagram asset', and lists supported formats (SVG, DWG, DXF), making the purpose relatively clear. It distinguishes from sibling tools like 'place_drawing_asset' by focusing on diagram assets.

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?

No guidance is provided on when to use this tool versus alternatives like 'place_drawing_asset'. There is no mention of prerequisites, context, or when not to use it.

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/liangjunglj-cpu/almond-mcp'

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