Skip to main content
Glama

photoglacier_close

Close the Photoglacier browser session after work is complete to stop credit usage and end the active connection.

Instructions

Close the Photoglacier browser session when the work is done, so credits stop running.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/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 burden, and it does add real value by disclosing the cost consequence (credits stop running). However, it is silent on whether closing discards session state or unsaved work, whether the close is reversible or re-openable, and whether cleanup happens server-side – all material for a terminate operation.

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 action front-loaded, followed by the timing condition and the reason. No filler, no restatement of the tool name, and every clause contributes information.

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 zero-parameter terminate tool with no output schema and no annotations, the description covers what it does, when to call it, and why it matters. The only meaningful omission is what happens to in-session state on close, which would matter if the agent may need to resume work.

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, so there is no parameter meaning to add; the baseline is 4. Nothing in the description misrepresents the input surface, and none is 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 gives a specific verb ('Close') and a specific resource ('the Photoglacier browser session'), making the operation unambiguous. It does not name the complementary sibling (photoglacier_open), but the operation is concrete enough that an agent can distinguish it from click/read/type/status siblings without opening any schema.

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?

It states an explicit trigger condition ('when the work is done') and a motivating reason ('so credits stop running'), which is clear positive guidance. It stops short of any when-not guidance or naming an alternative (e.g. leaving a session open for reuse), so it is not a full 5.

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