Skip to main content
Glama
Torque360 MCP Server

Torque360 MCP Server

torque360_click

Clicks a numbered element on the current Torque360 page to complete setup and confirmed write workflows in a signed-in cloud browser.

Instructions

Click a numbered element on the current Torque360 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": "torque360_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 provided, so the description carries the full behavioral burden and does not meet it. It never says whether a click navigates to a new page, mutates state, triggers irreversible actions, or what happens if the element number is stale or invalid.

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 resource, with no filler or redundancy. It is as short as a description can be while still naming the action and target.

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?

With no annotations and no output schema, the definition should disclose prerequisites (a preceding torque360_read) and side effects (does the page change, does it need a subsequent read?). Those omissions leave real ambiguity about how to sequence this tool relative to its siblings.

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 single parameter already documents that it is a 1-based element number from the last read. The description's phrase 'numbered element' restates that without adding format, range, or staleness guidance 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?

The description gives a specific verb (Click) and a specific resource (a numbered element on the current Torque360 page), so the action is unambiguous. It does not, however, differentiate itself from siblings like torque360_type or torque360_read, which also plausibly target numbered elements on the same page.

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: 'numbered element' plus the schema note 'Element number from the last read' hints that a prior read is required to obtain valid numbers. The description itself states no when-to-use condition and no alternative (e.g., when to use torque360_type instead of clicking a text field).

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