Skip to main content
Glama

fill

Type values into 5250 input fields without sending data to the host, so you can stage form entries and verify screen state before submission.

Instructions

Type values into input fields without sending anything to the host.

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": {
      "values": "<values>"
    },
    "name": "fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
expectNotext that must be on screen, or "row:text"
valuesYesfield -> value, e.g. {"5,25": "QSECOFR", "Option": "2"}; an empty string clears the field
sessionNosession name; lets you run several side by sidemain
screen_idNoscreen_id from your last read; refused if the screen changed

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so safety framing is already covered. The description usefully adds that nothing is transmitted to the host, which is real behavior beyond the annotations, but it says nothing about what happens on failed validation, partial fills, or a screen_id mismatch — the failure modes an agent most needs to anticipate.

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 short sentence, front-loaded with the action and immediately followed by the constraint that defines it. No filler, no restatement of the tool name.

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?

With an output schema and full parameter documentation available, the description needn't explain return values. However, for a state-mutating input tool with a nested field-to-value map, the description leaves out what the agent should expect on failure and how the operation relates to the surrounding session/screen workflow, leaving it merely adequate.

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 all four parameters (including the field-to-value map format, the clearing convention, session naming, and screen_id refusal) are already documented in the schema. The description adds no parameter meaning on top of that, which is the expected baseline 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 gives a specific verb and resource ("Type values into input fields") and adds a scope qualifier ("without sending anything to the host") that makes the operation's boundary concrete. It stops short of naming how this differs from sibling tools like keys or press, which is the only thing keeping it below 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 only implied: the phrase "without sending anything to the host" suggests this is the non-submitting half of an interaction, but the description never states when to choose fill over keys or press, nor any prerequisite (e.g., that a screen must be read first). An agent can infer intent but must reason about alternatives itself.

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