Skip to main content
Glama

Edit my shop profile

update_shop_profile
Destructive

Change your shop's public description or its default lead time in days. Needs a connected Printlooper account.

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

Input Schema

NameRequiredDescriptionDefault
descriptionNo
default_lead_time_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The description adds a genuine operational prerequisite ("Needs a connected Printlooper account") that annotations do not convey. However, with destructiveHint=true and zero required parameters, the crucial behavior — whether this is a partial update that leaves unspecified fields untouched, and what an empty call does — is never stated. Also silent on whether changes are immediately public.

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 action stated first and the prerequisite second; nothing is wasted. Slightly better structure would put the field list and the account requirement in a single front-loaded clause, but it is close to optimal for a simple two-param tool.

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 mutation tool with an empty required-parameter list, no output schema, and 0% schema documentation, the definition covers the basics (what fields, what units, what prerequisite). It falls short on partial-update semantics and post-change visibility, which an agent needs before invoking a destructive-flagged edit with no required arguments.

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; it does add useful meaning by calling the description "public" and specifying lead time is "in days." It still omits the schema constraints (2000-char cap, 1–30 day range) and never says both parameters are optional or how partial updates behave.

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?

Names a specific verb ("Change") and resource ("your shop's public description or its default lead time"), and enumerates exactly the two editable fields, which maps cleanly onto the read-only sibling get_my_shop. It is clear what the tool does, though it does not explicitly name the get counterpart as the way to read current values.

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?

Implies usage (editing the shop profile's description or lead time) and states the prerequisite of a connected Printlooper account. It offers no explicit when-not guidance and no mention of alternatives such as get_my_shop for viewing or other shop-setting tools, so the agent must infer context.

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