Skip to main content
Glama

ezee_optimus_type

Enter text into a specified numbered field on the current eZee Optimus page to fill forms and update records accurately.

Instructions

Type text into a numbered field on the current eZee Optimus 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": "ezee_optimus_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

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the entire behavioral burden and does not meet it. It never says whether typing replaces or appends existing content, whether it dispatches change/key events or triggers form submission, whether the element must be visible or focused first, or what happens on an invalid field number.

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?

One short, front-loaded sentence with no filler or repetition. It is efficient, though the terseness is part of why behavioral detail is absent rather than a virtue in itself.

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 simple two-parameter action tool with full schema coverage and no output schema, the description covers the basic what. It is still too thin for a mutation-style UI action with zero annotations, since the preconditions (page open, prior read) and effects are undeclared.

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 coverage is 100%, so both parameters (text, element) are already documented in structured form; baseline 3 applies. The phrase 'numbered field' reinforces that element is a positional index on the current page, but that meaning is already present in the schema's 'Field number from the last read'.

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?

A specific verb plus resource: 'Type text into a numbered field on the current eZee Optimus page.' An agent can tell this apart from click/read/close siblings without opening a schema. It stops short of 5 only because it never names the alternatives or the boundary conditions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance, no stated prerequisites, and no alternatives named among the six siblings. The only hint of ordering ('field number from the last read') lives in the schema, not the description, so the agent gets no explicit instruction to read the page first.

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