Skip to main content
Glama

swift_galleries_guide

Guides users through Swift Galleries screens to manage clients, room photos, wall designs, sales reports, order downloads, and the sign-in link; call it first before related tasks.

Instructions

How to work in Swift Galleries (clients, room photos, wall designs, sales reports and order downloads): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Swift Galleries, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It implies a read-only informational lookup that returns screens and a sign-in link, but it never states that it has no side effects, whether the response is text or a navigation payload, or how the guide relates to actually performing tasks afterward.

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?

A single front-loaded sentence lists the covered topics in a compact parenthetical and ends with the actionable instruction "Call this first." Nothing is redundant or padded.

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 one-optional-parameter informational tool with no output schema, the description sufficiently conveys subject matter, scope, and invocation ordering. The main remaining gap is what the returned guide actually looks like and whether further action tools are needed after reading it.

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 100%, and the single optional "task" parameter is already documented as "What you want done in Swift Galleries, in your words." The description adds no additional meaning about how the task string shapes the response, so the baseline of 3 applies.

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 the resource (a guide to Swift Galleries) and enumerates the domains it covers: clients, room photos, wall designs, sales reports and order downloads, plus screens and the sign-in link. That level of specificity lets an agent tell it apart from the action siblings like swift_galleries_click or swift_galleries_status, though it describes the content rather than a crisp verb+resource action.

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?

"Call this first" gives explicit ordering guidance relative to the other Swift Galleries tools, which is the key decision an agent faces here. It stops short of saying when not to call it or what to do after, so it is clear context without full exclusions.

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