Skip to main content
Glama

oto_photo_guide

Provides step-by-step guidance on oto.photo screens and the sign-in link so you can organize galleries, bookings, clients, gift certificates, and portfolio albums; call it first.

Instructions

How to work in oto.photo (organise galleries, bookings, clients, gift certificates and portfolio albums): 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": "oto_photo_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in oto.photo, 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?

No annotations are supplied, so the description carries the burden. It discloses the return content (screens overview and the sign-in link), which implies a read-only informational call, but it never says explicitly that nothing is mutated, nor whether the guidance is static or reflects live state. Adequate but thin for a tool with zero annotation coverage.

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 compact clauses: the domain list first, then the imperative "Call this first" as a punchy closer. The parenthetical enumeration is slightly dense but every item is informative; nothing is redundant.

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?

No output schema exists, and the description compensates by indicating the response contains screen guidance and a sign-in link. For a single-optional-parameter documentation tool with no annotations, that is enough for an agent to invoke it correctly, though a note on whether output is static or live would close the last gap.

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?

There is only one optional parameter and schema coverage is 100%, with the schema itself explaining "what you want done in oto.photo, in your words." The description adds no further meaning about the task string, so the schema does the work — baseline 3 applies.

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 the resource precisely ("How to work in oto.photo") and enumerates the domains covered — galleries, bookings, clients, gift certificates, portfolio albums — plus what it yields (screens and the sign-in link). An agent can tell this is an orientation/knowledge tool rather than an action tool like its click/type/open siblings.

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" is an explicit, unambiguous routing instruction that positions it ahead of oto_photo_open/click/type. It does not state when to skip it or re-call it, but the primary sequencing guidance is present and actionable.

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