Skip to main content
Glama
ConstructionOnline MCP Server

ConstructionOnline MCP Server

constructiononline_click

Clicks a numbered element on the current ConstructionOnline page to navigate or activate controls identified from the last page read.

Instructions

Click a numbered element on the current ConstructionOnline 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": "constructiononline_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 disclosure burden, and it omits key behavior: whether the click navigates, submits a form, or mutates state; whether the element numbering is invalidated afterwards; and what happens on failure. The only behavioral hint is the dependency on 'the last read,' which implies a stateful page snapshot without explaining it.

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 sentence, front-loaded with the verb and target, with zero redundant wording. Nothing needs trimming.

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?

This is a stateful UI-automation action with no annotations and no output schema, so the description needs to explain post-click consequences and state invalidation, and it does neither. An agent cannot tell from this definition whether clicking is safe to repeat, whether the page changes, or how to recover if the element number is stale.

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?

There is a single required parameter with 100% schema coverage, and the schema already explains it as the 'Element number from the last read.' The description only repeats 'numbered element' and adds no format, range, or error semantics beyond the schema, so the baseline of 3 is appropriate.

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?

States a specific verb (click) and a specific target (a numbered element on the current ConstructionOnline page), which is clearly distinct from siblings like read, type, or open. It could have gone further by contrasting with constructiononline_type, which also acts on page elements, but the action is unambiguous.

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?

The phrase 'numbered element' plus 'from the last read' implicitly tells the agent to call the read tool first and to use the numbering it produced. However, it never explicitly states when to click versus when to type, nor what to do if the page has changed since the last read, so the sequencing is inferred rather than instructed.

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