Skip to main content
Glama

photoglacier_type

Types text into a numbered field on the current Photoglacier page to fill inputs identified during a prior read.

Instructions

Type text into a numbered field on the current Photoglacier 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": "photoglacier_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.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It does not say whether typing replaces or appends to existing field content, whether it submits the form or triggers navigation, what happens on an invalid field number, or what the call returns — all material for an interaction tool that mutates page state.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of why behavioral details are absent.

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?

For a two-parameter tool with full schema coverage and no output schema, the definition is minimally sufficient to invoke. It is missing state context — whether the page must already be open and read, and whether the action has side effects beyond text entry — which matters for an interactive browser tool.

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 schema itself already explains 'element' as 'Field number from the last read' more precisely than the description does. The description adds only the framing that the field is 'numbered' on the 'current' page, so it neither compensates for nor extends the schema.

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 concrete verb ('Type text') and target ('a numbered field on the current Photoglacier page'), which is enough to distinguish it from photoglacier_read or photoglacier_click. It stops short of explicitly naming the siblings it is not, so it lands at 4 rather than 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?

Usage is implied by the phrase 'current Photoglacier page' and by the schema note tying 'element' to 'the last read', suggesting a read-then-type sequence. However, the description never states prerequisites (page must be open, field number must come from a prior read) or when to prefer click/read instead, so guidance is only inferable.

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