Skip to main content
Glama

Save business profile

save_business_profile
DestructiveIdempotent

Save facts about the account's business: what it sells, who writes in, the tone it wants, its languages, opening hours and escalation policy. Only the fields passed change; the rest keep their current value, which get_business_profile shows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_business_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNo
websiteNo
audienceNo
industryNo
productsNo
languagesNo
descriptionNo
support_hoursNo
top_questionsNo
escalation_policyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=true; the description adds the genuinely useful merge semantics — "only the fields passed change; the rest keep their current value" — which an agent cannot infer from the hints. It does not explain how to clear a field or how array fields (products, languages, top_questions) are treated on repeat calls, which matters given destructiveHint=true.

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?

Two tight sentences with no filler; the payload scope is front-loaded and the partial-update rule follows immediately. Every clause carries information an agent needs.

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 10-parameter, all-optional mutation tool with no output schema and no per-parameter documentation, the description is adequate but incomplete: it omits a third of the fields and says nothing about replacing versus appending array values or clearing an existing value. The core partial-update contract is present, which keeps it at minimum-viable-plus rather than lower.

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 0%, so the description carries the burden and does partially discharge it by mapping plain-language concepts to fields (what it sells → products, who writes in → audience, opening hours → support_hours, escalation policy). However, four of the ten parameters — website, industry, description, top_questions — are never mentioned, and no format or length guidance is added beyond the schema constraints.

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 ("Save") and resource ("the account's business") and enumerates the concrete facts stored: products, audience, tone, languages, support hours, escalation policy. Naming get_business_profile as the read counterpart makes the write/read split unambiguous.

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?

Usage context is clear — use this to persist business facts, and read them back with get_business_profile. It stops short of explicit exclusions or prerequisites (e.g., who may call it, whether it can be used before a profile exists), so it is a strong 4 rather than a 5.

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.

Resources