Skip to main content
Glama

oto_photo_open

Opens an oto.photo page in your signed-in Cloud Browser so you can manage galleries, bookings, clients, gift certificates, and portfolio albums.

Instructions

Open a oto.photo page in your signed-in Cloud Browser (default https://oto.photo/auth) to work with organise galleries, bookings, clients, gift certificates and portfolio albums.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://oto.photo/auth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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. It usefully discloses that the browser is already signed in (no auth step needed) and supplies the default landing URL, but says nothing about what happens on failure, whether the session persists for later click/read calls, or what the call returns.

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?

One front-loaded sentence with the verb and default URL early; no filler. Minor deductions for awkward grammar ("a oto.photo", "to work with organise galleries") that slightly hurts readability.

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?

No annotations and no output schema, so the description is the only source of behavioral information, and it omits return values and cross-call state. For a simple one-parameter navigation tool this is adequate but leaves an agent guessing about what it gets back.

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% for the single optional url parameter, and the description only restates the default value already present in the schema. It adds no format, constraint, or example semantics beyond that baseline.

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?

States a specific verb ("Open") and resource ("oto.photo page") plus the execution environment ("signed-in Cloud Browser"), which separates it from interaction siblings like oto_photo_click or oto_photo_read. It does not explicitly name a sibling or state the division of labour, so it stops short of 5.

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?

The trailing clause enumerates the workflows it enables (galleries, bookings, clients, gift certificates, portfolio albums), which implies it is the entry point before other browser actions. There is no explicit when-not guidance or reference to alternatives such as oto_photo_guide or oto_photo_status.

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