Skip to main content
Glama

ie_upload

Sets a file input from a local file path during IE-mode automation; uploads are limited to the directory configured by IE_UPLOAD_DIR.

Instructions

Set a file by sending a local file path. Only files inside the directory configured with IE_UPLOAD_DIR can be uploaded (disabled when it is unset).

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": {
      "by": "<by>",
      "value": "<value>",
      "path": "<path>"
    },
    "name": "ie_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYes
pathYesfile inside IE_UPLOAD_DIR: relative to it, or absolute
frameNo
valueYes
timeoutNoseconds to wait for the element (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/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 burden, and it does disclose one important trait: uploads are sandboxed to IE_UPLOAD_DIR and the tool is disabled when that variable is unset. It omits other behavior an agent needs — what happens on rejection, whether change/submit events fire, and the element-wait semantics.

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?

Two tight sentences with the core action front-loaded and the security constraint second. No filler, though the parenthetical about being disabled when unset could be read as part of the same constraint clause.

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?

A 5-parameter, 3-required interaction tool with no annotations and no output schema needs more than two sentences. The meaning of 'by'/'value' (locator strategy) and 'frame' scoping are entirely undocumented, leaving an agent unable to construct a correct call from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%; path and timeout are documented in the schema, but 'by', 'value', and 'frame' are undocumented in both places. The description mentions only the local file path concept and adds no meaning to the locator parameters or frame targeting, so it does not compensate for the coverage gap.

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 action and target: 'Set a file <input type=file> by sending a local file path.' That distinguishes it from generic input tools like ie_fill or ie_attach without naming them. Minor gap: it doesn't explicitly contrast with the similarly-named file-related sibling ie_attach.

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?

The mention of '<input type=file>' implies the situation — use this when the target element is a file input rather than a text field. However, no when-not guidance and no named alternatives (ie_fill, ie_attach) are given, so the agent must infer routing from sibling names alone.

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