Skip to main content
Glama

ontraccr_type

Types text into a numbered field on the current Ontraccr page using the field number from the last read, enabling agents to fill forms.

Instructions

Type text into a numbered field on the current Ontraccr 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": "ontraccr_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.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, but it does disclose two useful facts: it acts only on the 'current' page (a state dependency) and it targets a numbered field (implying sequencing after a read). It does not say whether typing replaces or appends existing text, whether it triggers submit/change events, or what happens with 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?

A single sentence with the verb front-loaded and zero filler. It is efficient, though it spends its only clause on purpose and leaves no room for any usage or behavioral guidance.

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 low-complexity, two-parameter tool with a fully documented schema and no output schema, this is close to adequate. However, with no annotations covering write semantics, key details about replacing text, submitting, and error handling are absent, leaving the agent to infer them.

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% and the schema already explains both parameters, including that 'element' is a field number from the last read. The description's phrase 'numbered field' restates rather than extends that meaning, so the baseline of 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 names a specific verb ('type text') and a specific target ('a numbered field on the current Ontraccr page'), which distinguishes it from read-only siblings like ontraccr_read and from ontraccr_click. It stops short of explicitly naming an alternative tool, but the action is unmistakable.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The only hint about the precondition (the field number comes from a prior read) lives in the schema's parameter description, not in the tool description itself.

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