Skip to main content
Glama

Update store name and logo

update_store
DestructiveIdempotent

Sets a store's public name and logos, which Leal uses on cards, posters and signup pages. Logos are fetched from public image URLs (PNG, JPEG, WebP, GIF or SVG). Replaces the current values.

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": "update_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentNoOptional. One short sentence on what the person asked you to do, e.g. "Set up a stamp card for Ground Up Café". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.
logo_urlNoPublic https URL of the wide logo.
store_idNoStore id from list_stores. Optional when the login has one store.
store_nameNoThe business name customers know, e.g. "Bean There Coffee".
square_logo_urlNoPublic https URL of a square logo or icon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / intent
      Added value: +{
      +  "description": "Optional. One short sentence on what the person asked you to do, e.g. \"Set up a stamp card for Ground Up Café\". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is carried by structured data. The description still adds real context beyond that: the values are publicly visible on cards/posters/signup pages, logos are fetched from external public URLs, and 'Replaces the current values' corroborates the destructive hint. The gap is that it never resolves whether a call with only store_name wipes the logos — the single most important behavioral question for a destructive, all-optional-parameter 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?

Three short sentences with the effect and public visibility front-loaded, followed by the input constraint and the replacement semantics. No filler, no repetition of the title, and each sentence contributes new 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?

With no output schema needed, full parameter documentation, and annotations covering safety and idempotency, the definition is nearly complete for a small update tool. The missing piece is partial-update semantics — whether omitted fields are preserved or cleared — which matters given destructiveHint=true and zero required parameters.

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 100%, so the baseline is 3, and the description largely restates what the schema documents. It does add marginal meaning by enumerating the accepted image formats (PNG, JPEG, WebP, GIF, SVG) and stating that logo sources must be public URLs, but it says nothing about intent, store_id resolution, or the required-store-id-when-multiple-stores rule.

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 names a specific verb and resource ('Sets a store's public name and logos') and adds where those values surface (cards, posters, signup pages), which makes the effect concrete. It stops short of contrasting itself with siblings such as create_store or the other update_* tools, but the name/resource pair is distinctive enough that an agent can identify it.

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 a store's public name or logo must change. There is no explicit when-not guidance, no mention of what to do instead (e.g. create_store for new stores, get_brand_kit to inspect assets), and no stated prerequisites such as needing store_id from list_stores despite that being a live concern.

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