Skip to main content
Glama
Torque360 MCP Server

Torque360 MCP Server

torque360_open

Opens a Torque360 page in your signed-in Cloud Browser (default portal) to access shop reports, technician hours, inspection templates, and pricing.

Instructions

Open a Torque360 page in your signed-in Cloud Browser (default https://portal.torque360.co) to work with shop reports, technician hours, inspection templates and pricing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "torque360_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://portal.torque360.co

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the browser is already signed in, which tells the agent no authentication step is needed, but it says nothing about navigation semantics: whether this replaces the current page or opens a new one, whether state is lost, or whether torque360_close is needed afterward. For a state-changing navigation tool, that is a meaningful gap.

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?

A single sentence with the verb and default URL front-loaded and no redundant or filler wording. Every clause contributes purpose or scope information.

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?

The tool is simple (one optional parameter, no output schema) and the description covers purpose, environment, and default target adequately. It stops short of explaining session behavior relative to torque360_close and whether repeated opens stack pages, which an agent coordinating a browser session would need.

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?

Only one optional parameter and schema description coverage is 100%, so the schema already documents the URL and its default. The description restates the same default URL, adding no new meaning such as accepted path formats, relative vs absolute URLs, or behavior when the URL is omitted. Baseline 3 given full schema coverage.

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 and resource ('Open a Torque360 page'), names the execution environment ('signed-in Cloud Browser'), gives the default URL, and lists representative content (reports, technician hours, templates, pricing). It is clear what the tool does, though it does not explicitly differentiate itself from siblings like torque360_read or torque360_close.

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 clause 'to work with shop reports, technician hours, inspection templates and pricing' implies the context in which to use it, but there is no explicit when-not guidance, no prerequisites, and no naming of alternatives such as torque360_status or torque360_read. Usage is implied rather than prescribed.

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