Skip to main content
Glama

photoglacier_guide

Guides you through Photoglacier setup: learn the screens, find the sign-in link, prepare galleries, and read client activity before using other actions.

Instructions

How to work in Photoglacier (prepare galleries and read client activity): 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": "photoglacier_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Photoglacier, in your words.

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, the description must carry the behavioral burden: it implies a read-only informational lookup and lists what the content covers. It does not state whether the call mutates anything (unlikely but unstated) or whether the response is prose instructions versus a URL to open, which leaves the agent guessing about output shape.

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 short sentences with the actionable directive placed last and the content summary first. The parenthetical listing could be trimmed slightly, but nothing is wasted.

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 simple single-parameter guide tool with no output schema, the core is present: what it covers and that it should run first. Missing is any hint of what comes back (instructions text, sign-in URL, screen list) or what to do next 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?

The single 'task' parameter is fully described in the schema (100% coverage), so the baseline is 3. The description adds no guidance on how to phrase the task or whether it can be omitted (it is not required), so it neither compensates nor detracts.

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 states that this is a guide to working in Photoglacier, naming concrete content (screens, sign-in link, preparing galleries, reading client activity). That distinguishes it from the UI-action siblings like photoglacier_click or photoglacier_open, though the phrasing 'How to work in' is looser than a clean verb+resource statement.

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 an explicit ordering directive that an agent can act on before invoking any sibling. It stops short of saying when not to use it or what to do after the initial call, but the primary usage condition is unambiguous.

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