Skip to main content
Glama

oto_photo_type

Types text into a chosen numbered field on the current oto.photo page, using the field number from the last read to enter data in the correct form field.

Instructions

Type text into a numbered field 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>",
      "text": "<text>"
    },
    "name": "oto_photo_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden and doesn't meet it. It does not say whether typing replaces or appends to existing field content, whether it focuses/submits the field, what happens with an invalid element number, or whether the page must be open at all.

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 front-loaded sentence with no filler; the action and target come first and nothing is wasted. It is short but not so terse as to be meaningless.

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?

The tool is simple (two required params, no nesting, no output schema), so a short description is defensible, but the missing prerequisites — an open page and a prior read to obtain a valid element number — are exactly the details an agent needs before invoking it.

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%, so both 'element' and 'text' are already documented in the schema, including that element is a field number from the last read. The description adds only the phrase 'numbered field,' which restates the schema rather than extending it (e.g., no note on field numbering stability or length limits).

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 ('Type text') and a specific target ('a numbered field on the current oto.photo page'), which distinguishes it from the click/read/status siblings by action type. It stops short of explicitly naming which sibling to use instead, but the action itself is unambiguous.

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?

Usage is only implied: 'current oto.photo page' hints that a page must already be open, and the schema's 'Field number from the last read' implies a prior oto_photo_read call, but the description never states prerequisites or when to prefer click vs type. No alternatives or exclusions are given.

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