Skip to main content
Glama

areas_create_area

Create a new area in your smart home by providing a name. Organize devices and scenes under this area for efficient management.

Instructions

Create a new area.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'create_area' (registered under namespace 'areas'). It takes a name string and delegates to ha_client.create_area.
    @mcp.tool()
    def create_area(name: str) -> dict:
        """Create a new area."""
        return ha.create_area(name)
  • server.py:34-34 (registration)
    The 'areas' FastMCP server is mounted at namespace 'areas', so the tool's full name becomes 'areas_create_area'.
    mcp.mount(areas_mcp, namespace="areas")
  • The HA client helper that sends a WebSocket call 'config/area_registry/create' to Home Assistant.
    def create_area(name: str) -> dict:
        return _ws_call("config/area_registry/create", name=name)
Behavior2/5

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

No annotations provided. Description only states the action without disclosing side effects, permissions, or error conditions. For a mutation tool, more transparency is needed.

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?

Single sentence is extremely concise and front-loaded. No wasted words.

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?

Despite having an output schema, the description lacks usage guidelines, parameter semantics, and behavioral context, making it insufficient for an agent to use correctly.

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?

Schema has 0% description coverage. Description does not mention the 'name' parameter or add any meaning beyond the schema, leaving the agent without guidance on its format or semantics.

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?

Description clearly states 'Create a new area.' with specific verb and resource. It distinguishes from sibling area tools like list, delete, control, etc.

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 on when to use this tool versus alternatives. No context about prerequisites or typical scenarios.

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/Fistacho/ha-nexus-agent'

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