Skip to main content
Glama

pic_time_type

Type text into a numbered field on the current Pic-Time page using a field number from the last read to fill forms or update gallery details.

Instructions

Type text into a numbered field on the current Pic-Time 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": "pic_time_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.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it says nothing about whether typing replaces or appends to existing field content, whether it triggers form submission or validation, or what happens if the element number is stale. For a mutating browser-automation tool this is a substantial gap.

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 redundant wording; the action and target come first. It is efficient, though its brevity contributes to the missing behavioral detail noted elsewhere.

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 state-mutating interaction tool with no annotations and no output schema, the definition should at least cover the read-then-type dependency and post-conditions such as whether the text is committed immediately. Neither is present, leaving an agent to infer critical sequencing.

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 'text' and 'element' are already documented, and the description adds only the notion that the field is numbered and lives on the current page. That is a marginal addition consistent with the baseline 3 when the schema does the heavy lifting.

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 states a specific verb ('type text') and target ('a numbered field on the current Pic-Time page'), which is enough to distinguish it from sibling tools like pic_time_click and pic_time_read. It stops short of explicitly naming the read tool whose output supplies the field number, so differentiation is implied rather than stated.

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 context is only implied: the schema note 'Field number from the last read' hints that a prior read is a prerequisite, but the description never says so directly. There is no explicit when-to-use versus when-to-use-a-sibling guidance and no stated preconditions or ordering.

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