Skip to main content
Glama

save_business_service_area

Idempotent

Update the business service area or existing website. Pass an empty string to clear a field.

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_service_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceAreaNo
existingWebsiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the operation non-read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavior not in the annotations: an empty string clears a field. However, it never states whether omitting a property leaves it unchanged (partial update) or wipes it, which is the critical ambiguity for a zero-required-parameter save tool.

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 short sentences, front-loaded with the action and resource, with the clearing rule as a second beat. Nothing is padded or redundant.

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 two-field, no-required-parameter mutation with no output schema and reasonably informative annotations, the definition covers the essentials plus the non-obvious clearing behavior. The remaining gap is the partial-vs-full update semantics, which is significant but narrow.

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 must carry the load, and it does partially: it names both updatable fields and defines the empty-string clear semantics that the schema does not. It adds nothing about expected format for existingWebsite (e.g. whether a full URL is required) or the interaction between the two fields.

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?

The description uses a specific verb ('Update') against a named resource ('business service area or existing website'), which maps cleanly onto the two schema properties and pairs obviously with the sibling get_business_service_area. It does not explicitly name that getter or distinguish itself from other save_* siblings, so it falls short of a 5.

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?

There is no statement of when to use this versus the sibling getter or other save_* tools, and no prerequisites or side-effect context. The only guidance offered is the empty-string clearing convention, which is a parameter rule rather than usage routing.

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