Skip to main content
Glama

photoglacier_open

Opens a Photoglacier page in your signed-in Cloud Browser so you can work with prepare galleries and read client activity.

Instructions

Open a Photoglacier page in your signed-in Cloud Browser (default https://photoglacier.com/app/login) to work with prepare galleries and read client activity.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://photoglacier.com/app/login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does contribute one meaningful fact: the browser is already signed in, so no auth step is needed. It does not disclose whether an existing tab is reused or a new one created, what happens with an invalid or off-domain URL, or any error/timeout behavior.

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?

A single front-loaded sentence with the action first and the purpose trailing; nothing is redundant, though the parenthetical default URL duplicates the schema and slightly bloats the line.

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-parameter navigation tool with no output schema and no annotations, the definition supplies enough to call it correctly: what it does, where it operates, and that the session is authenticated. Missing only edge-case behavior, which is minor at this complexity.

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% and the single optional `url` parameter is already documented with its default in the schema, so the description adds nothing beyond restating the same default login URL. Baseline 3 is appropriate when the schema does all the work.

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 gives a specific verb and resource ("Open a Photoglacier page") plus the environment it acts in ("your signed-in Cloud Browser") and the downstream goals (prepare galleries, read client activity). It is distinguishable from click/read/type siblings by verb alone, though it never explicitly names what it is not.

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?

It implies the context of use – you open a page in order to work with prepare galleries or read client activity – but gives no explicit when-not conditions, no prerequisite ordering relative to photoglacier_status or photoglacier_guide, and no guidance on whether this is the required entry point before the other tools.

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