Skip to main content
Glama

Update Business Info

update_business_info
DestructiveIdempotent

Update the business information that appears across the site — name, phone, email, address, hours, services list, etc. Changes propagate to all pages that reference this info.

Annotations: read-only=false, destructive=true, idempotent=true, open-world=false. Why: Overwrites the business name, contact details and hours on the DRAFT — a non-additive update, so destructive by the MCP definition; idempotent (the same input yields the same state); closed-world. The live site changes only when the user confirms publish_site; the draft stays editable in the Zarla editor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>"
    },
    "name": "update_business_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoBusiness name
emailNo
phoneNo
addressNo
site_idYes
taglineNoBusiness tagline / slogan
servicesNoList of services offered
opening_hoursNoStructured weekly hours — one entry per day
license_numberNo
years_in_businessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The description adds real context beyond the annotations: changes 'propagate to all pages that reference this info,' which tells the agent this is a site-wide single-source edit rather than a per-page tweak. The annotations already declare destructive/idempotent/closed-world and explain the draft-vs-live split, so the bar is lower here; the one gap is that the description never says whether omitted fields are preserved or cleared.

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?

Two tight sentences with the resource and the field list front-loaded, and the propagation behavior called out as a second beat. The trailing 'etc.' weakens the precision slightly by implying unspecified fields without naming them.

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

Completeness3/5

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

For a ten-parameter destructive mutation with no output schema, the definition covers the site-wide propagation effect but leaves the most consequential unknown unresolved: partial-update semantics for unset fields. Combined with the un-enumerated parameters, an agent could invoke it correctly but not confidently predict the resulting state.

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 40%, so the description must carry weight, and it names six of the ten fields (name, phone, email, address, hours, services) but omits tagline, license_number, years_in_business and site_id entirely. It also says nothing about whether this is a merge or a full replace, which matters most for a destructive tool with a single required parameter.

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?

States a specific verb and resource ('Update the business information') and enumerates the affected fields — name, phone, email, address, hours, services list — so an agent can tell it apart from update_header, update_footer and update_design. It stops short of naming those siblings or drawing an explicit boundary, which keeps it at 4 rather than 5.

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?

Usage is only implied: an agent infers it should call this when the site's core business details change. There is no explicit when-to-use / when-not-to-use statement and no pointer to publish_site as the follow-up step — that routing only appears in the annotation rationale, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.