Skip to main content
Glama

Growomat

by com.growomat
OverviewDiscussionsAdmin

Update business

update_business

Partial update of a business. 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 updated object. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body matching the BusinessUpdate schema. Fields below; see the OpenAPI spec for nested object shapes.
space_idNoOverride 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.
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish a non-read-only, non-destructive mutation, so the bar is lower. The description adds that it returns the full updated object and that brand changes affect all generated ad and social copy, which is meaningful behavioral context beyond the annotations; it doesn't cover validation failures or permission requirements.

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?

Three sentences, front-loaded with the operation and scope, with no wasted phrasing. The brand explanation and Space override note are each directly actionable.

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 mutation with nested objects and no output schema, the description covers the return ('full updated object'), the Space scoping mechanism, and the most complex parameter group. Only error/validation behavior is left unaddressed, which is minor.

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 coverage is 67% and the schema already documents the brand fields, tone dial ranges, and space_id in detail. The description reinforces the brand object's purpose but adds little beyond the schema for business_id or the body's other fields, so the baseline of 3 is appropriate.

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?

States a specific verb and resource ('Partial update of a business') and immediately scopes it as partial rather than a create/delete, which distinguishes it from the create_business and delete_business siblings. The mention of the brand object and Space scoping adds concrete detail about what can be updated.

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 word 'partial' signals when to use this over create_business, and the Space sentence gives explicit routing: use set_active_space to switch, or pass space_id for a one-call override. It stops short of describing when-not to use it or any prerequisites for updating a business.

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

All Growomat toolsInspect
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