Skip to main content
Glama

crexi_type

Types text into a numbered field on the current Crexi page, using the field index from the last read to fill forms and update listing data.

Instructions

Type text into a numbered field on the current Crexi 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": "crexi_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 at all, the description carries the full behavioral burden, yet it does not say whether typing replaces or appends to existing field content, whether it submits the form or fires keystroke events, what happens if the field number is stale or invalid, or whether the page state changes. It only conveys that the action targets the current page.

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?

It is a single front-loaded sentence with no filler, and the target context is stated first. Its brevity is close to ideal for a simple automation action, though it is terse enough to leave the noted behavioral gaps.

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 stateful browser-automation mutation with no annotations and no output schema, the description says nothing about success/failure signaling, focus requirements, or whether the typed value persists or submits. An agent can form the call but cannot predict its side effects.

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 parameters (text, element) are already documented with the key detail that the element number comes from the last read. The description's "numbered field" and "current Crexi page" add only marginal clarification, so the baseline 3 applies.

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") and target ("text into a numbered field on the current Crexi page"), which is clearly distinguishable from siblings like crexi_click or crexi_read. It stops short of naming those siblings, so it earns a 4 rather than a 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 "current Crexi page" and the schema's "field number from the last read" hint that a read must precede typing, but the description never states that prerequisite or says when to type versus click. No when-not-to-use conditions or alternatives are given.

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