Skip to main content
Glama

swift_galleries_status

Verify your Cotlet.dev account, credits, and Swift Galleries connection are ready before managing studio clients or designing walls.

Instructions

Check that your Cotlet.dev account and Swift Galleries are ready: account, credits and Swift Galleries connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose the three things being validated (account, credits, connection), which is meaningful. However, it says nothing about whether the tool is read-only, whether it makes network calls or has latency/auth implications, or how failure is signaled.

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 sentence with the purpose front-loaded and the three checked items listed compactly after the colon. No redundant clauses or filler.

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 zero-param diagnostic tool with no output schema, the description should indicate what kind of result an agent will get (a boolean pass/fail versus a report of individual problems) and what a failing check means for subsequent calls. That return-shape information is absent, leaving the agent to call it blind about the result format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is trivially empty, so there is nothing for the description to disambiguate. The baseline of 4 applies since no parameter semantics are needed.

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 ("Check") and concrete resources (Cotlet.dev account, credits, Swift Galleries connection), so the agent knows this is a readiness/preflight validation tool. It implicitly contrasts with the sibling browser-action tools (open, click, type, read, close), though it never names them explicitly.

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: the framing "are ready" suggests calling this before performing gallery actions, which is a natural preflight pattern. There is no explicit statement of when NOT to call it, no prerequisites, and no reference to what to do if a check fails.

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