Skip to main content
Glama

oto_photo_click

Clicks a numbered element on the current oto.photo page, letting an AI agent activate the corresponding on-page control.

Instructions

Click a numbered element on the current oto.photo page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "oto_photo_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. Clicking is a state-changing action that could navigate, submit, or mutate the page, yet the description says nothing about side effects, whether the page changes afterward, or what happens if the element number is stale or no longer present.

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 short sentence with no filler, and the action plus target are front-loaded. It is efficient, though so terse that it borders on under-specification rather than crisp precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-annotation interaction tool that mutates page state, an agent needs to know the ordering dependency on oto_photo_read and what to expect after the click; neither is stated. The 100% schema coverage of the lone parameter helps, but the behavioral picture remains incomplete.

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 description coverage is 100% and the single parameter is already documented as "Element number from the last read" with a minimum of 1. The description adds no additional meaning beyond that, so the baseline of 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?

"Click a numbered element on the current oto.photo page" gives a specific verb (click) and a specific target (a numbered element on the current page), which separates it from oto_photo_read or oto_photo_open. It stops short of explicitly distinguishing it from oto_photo_type, which also acts on numbered elements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use guidance, no prerequisites, and no named alternative among the six siblings. The only hint about where the element number originates ("from the last read") lives in the schema, not the description, so an agent must already know it needs oto_photo_read first.

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