arcpro-mcp

by qiobn

Overview Schema Source Related Servers Discussions Admin

Python

Local

Create Layout

create_layout

Create a print layout with a map frame. Set width, height, units (INCH, CENTIMETER, MILLIMETER, POINT), and margin.

Instructions

Create a print layout with a map frame already added. units: INCH (default), CENTIMETER, MILLIMETER, POINT. Then call export_layout to write it to disk.

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": "create_layout"
  }
}

Input Schema

Name	Required	Default
`name`	No	Layout
`map_name`	No
`width`	No
`height`	No
`units`	No	INCH
`margin`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It reveals that the layout comes with a map frame pre-added and mentions supported units, but lacks information on whether the layout is automatically saved, if it requires an active project, or any potential side effects.

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

Conciseness4/5

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

The description is two sentences long, front-loading the primary purpose. The second sentence about export_layout is concise and adds workflow context without unnecessary details. No filler or redundancy.

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, 0 required, no annotations, and an output schema that is not explained, the description is incomplete. It does not describe the return value, whether the layout is persisted in the project, or how it relates to other tools like 'create_map' or 'export_layout' beyond a simple workflow hint.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the description does not detail individual parameters. It only lists the units enum values but fails to explain the purpose or constraints of parameters like name, map_name, width, height, and margin. The description adds minimal value beyond the schema's defaults.

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 'Create a print layout with a map frame already added', which specifies the verb and resource. It distinguishes from the sibling 'create_map' tool by focusing on print layouts, but does not explicitly differentiate from other sibling tools like 'export_layout', though it hints at a workflow.

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 description suggests a workflow by saying 'Then call export_layout to write it to disk', implying that create_layout is used before export_layout. However, it provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions.

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