Skip to main content
Glama
Khaif004

SIA MCP Server

by Khaif004

Create Area

sia_create_area

Create a new geographic area with polygon boundary, validity period, and type for field or crop zone management. Returns the area ID.

Instructions

Create a new geographic area in the SIA AreaService.

Areas define the boundary polygon for a field or crop zone. Returns the created Area ID.

Args:

  • name (string): Display name of the area

  • validFrom (string): ISO datetime from which the area is valid, e.g. "2026-01-01T00:00:00.000Z"

  • validTo (string, optional): ISO datetime until which the area is valid; omit for indefinite

  • areaType_ID (string): UUID of the area type

  • boundary_geojson (string): GeoJSON string defining the area polygon

  • isAutomaticallyCalculated (boolean): Whether area size is auto-calculated from geometry

  • areaSize (number, optional): Manual area size in hectares (used when isAutomaticallyCalculated=false)

  • isBlocked (boolean, optional): Whether the area is blocked (default: false)

Returns: Created Area object with ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name of the area
validToNoISO datetime or null for indefinite
areaSizeNoManual area size in hectares
isBlockedNoWhether area is blocked
validFromYesISO datetime, e.g. '2026-01-01T00:00:00.000Z'
areaType_IDYesUUID of the area type
boundary_geojsonYesGeoJSON string for the area polygon
isAutomaticallyCalculatedYesAuto-calculate area from geometry
Behavior4/5

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

Annotations already indicate it's a creation (not read-only, not destructive). The description adds that it returns the created Area ID, providing additional behavioral context beyond annotations.

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 concise with a brief intro, a clear list of parameters in a code-block style, and a returns statement. Every sentence serves a purpose.

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

Completeness5/5

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

Given 8 parameters and no output schema, the description thoroughly explains each parameter and the tool's purpose. It is complete for the tool's role.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the relationship between isAutomaticallyCalculated and areaSize, and providing example values for validFrom.

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

Purpose5/5

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

The description clearly states 'Create a new geographic area in the SIA AreaService' and explains that areas define boundary polygons for fields or crop zones. This distinguishes it from sibling tools like sia_create_field or sia_create_crop_zone.

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

Usage Guidelines4/5

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

The description indicates when to use this tool (to create an area defining a boundary polygon). It does not explicitly mention when not to use it, but the sibling list provides context for alternatives.

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/Khaif004/SIA_MCP'

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