Growomat

Create business

create_business

Register a new business: its name and website, plus optional description, target groups, SEO keywords, key pages (sitelinks) and a brand voice profile. The optional brand object is the business's brand voice profile — tone dials (formality, energy), voiceNotes, promises and bannedPhrases — and governs all generated ad and social copy for this business. Returns the full created object. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.

Input Schema

Name	Required	Description	Default
`body`	Yes	Request body matching the BusinessCreate schema. Fields below; see the OpenAPI spec for nested object shapes.
`space_id`	No	Override the active Space for this one call. Defaults to the active Space set via set_active_space (or GROWOMAT_SPACE_ID on the server). Pass to read/write a different Space without changing the session binding.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / body / properties / categoryId

Added value: +{
+  "description": "The business category, an id from *Get the creative vocabulary* (`businessCategories`). Used to compare results with similar businesses.",
+  "type": "string"
+}

First observedAug 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only but non-destructive write operation. The description adds that it returns the full created object and that the brand profile governs generated ad and social copy, along with Space scoping details; it does not cover auth requirements or duplicate/failure behavior.

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 front-loaded with the core action and fields, then covers the brand profile, return behavior, and Space scoping. The sentences are compact and each adds useful information.

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

Completeness4/5

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

For a create tool with a complex nested body but full schema coverage, the description does enough: it names required name/website, summarizes optional fields, explains brand behavior, states the return shape, and documents Space scoping. Minor gaps around auth, duplicate handling, and advanced fields remain but are not critical for correct invocation.

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?

Schema description coverage is 100%, so the schema already carries most parameter meaning. The description adds useful context for key pages as sitelinks and explains the brand profile's role, but it omits fields such as status, categoryId, logoUrl, and logoSource.

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 uses a specific verb and resource, 'Register a new business', and immediately lists the core fields it accepts. This clearly separates it from retrieval tools like get_business or list_businesses and mutation tools like update_business.

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?

It explains the Space scoping behavior and names set_active_space as the way to switch, plus the space_id one-call override. It does not explicitly say when to use this versus update_business or how duplicate businesses are handled, but the intended context is clear.

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

All Growomat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?