Skip to main content
Glama

ontraccr_click

Clicks a numbered element on the current Ontraccr page, enabling agents to interact with page controls identified during the last read.

Instructions

Click a numbered element 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>"
    },
    "name": "ontraccr_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly does not. It does not say whether clicking navigates or mutates page state, whether the element list becomes stale afterward, whether the tool waits for the page to settle, or what happens if the element number is invalid or no longer present.

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 resource, with no filler or redundant clauses. Nothing could be cut without losing information.

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 browser-automation click with no annotations and no output schema, the agent needs to know post-click effects, staleness of the element numbering, and failure behavior. None of that is present, leaving the agent to guess before invoking a state-changing action.

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% and the single parameter is fully documented in the schema ('Element number from the last read'). The description restates the 'numbered element' idea without adding validation, staleness, or failure semantics beyond the schema.

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?

Specific verb (Click) plus a scoped resource ('numbered element on the current Ontraccr page'), which is distinguishable from the typing and reading siblings by implication. It stops short of naming a sibling or stating explicitly how it differs from ontraccr_type or ontraccr_read.

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: 'element number from the last read' hints that a read must precede the click, and 'current page' scopes when it applies. There is no explicit when-to-use statement, no statement of prerequisites, and no mention of what to do instead if the target is a text field.

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