Skip to main content
Glama

oto_photo_read

Reads the current oto.photo page to extract visible text and numbered buttons, links, and fields; optionally target one element for focused inspection.

Instructions

Read the current oto.photo page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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?

With no annotations, the description carries the full behavioral burden. It does establish the safe read-only nature and describes the returned content, but it says nothing about whether the page must already be open, whether the result is a snapshot after scrolling, or any limits on what gets enumerated.

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?

One front-loaded sentence with no filler: subject, action, and the four kinds of content returned. Nothing to cut.

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 read tool with no output schema, the description adequately covers the return content, which is the main thing an agent needs. The remaining gap is relational: it does not clarify how it differs from oto_photo_status, which matters given how similar those two names are.

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 a single optional parameter and the schema already documents it at 100% coverage ('Read only inside this element'). The description adds no interpretation of what scoping to an element means in practice, so the schema is doing all the work and 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?

States a specific verb ('read') and resource ('the current oto.photo page'), and goes further by enumerating what a read yields: text, numbered buttons, links and fields. That clearly separates it from oto_photo_click/type/close, but it gives no help distinguishing it from the sibling oto_photo_status, which sounds like it could also return page information.

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?

There is no explicit when-to-use or when-not-to-use statement. Usage is only implied: the mention of 'numbered buttons' hints that this tool is what produces the indices used by oto_photo_click, but the agent must infer that relationship rather than being told it.

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