Skip to main content
Glama
Torque360 MCP Server

Torque360 MCP Server

torque360_guide

Explains how to navigate Torque360, including shop reports, technician hours, inspection templates, pricing, and the sign-in link. Call this first before other tasks.

Instructions

How to work in Torque360 (shop reports, technician hours, inspection templates and pricing): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Torque360, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does signal that this is an informational/orientation call whose content is screens and a sign-in link rather than an action. It does not state that the tool performs no mutation, how the response is shaped, or how the optional task input changes the answer, leaving real gaps for an annotation-free tool.

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?

One compact sentence, front-loaded with the domain list and closed with the imperative 'Call this first', so the most actionable instruction lands where it is read. The parenthetical list is slightly dense but every element maps to real coverage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter, no-output-schema guide tool, the definition covers what the tool is, what it returns conceptually, and when to reach for it. Only the absence of any note on response shape or follow-up routing after orientation keeps it from being fully complete.

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 optional 'task' parameter is already described as 'what you want done in Torque360, in your words', so the schema does the documentation work. The description frames the tool as task-oriented but adds no detail on how phrasing the task affects the returned guidance.

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 the resource concretely: guidance on how to work in Torque360, enumerated as shop reports, technician hours, inspection templates, and pricing, plus screens and the sign-in link. That is enough for an agent to distinguish this informational tool from the action siblings (click, open, read, type). It stops short of explicitly naming which sibling to use once oriented.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first' gives an explicit ordering rule that no sibling name alone would establish, which is exactly the guidance an agent needs for an orientation tool. There are no when-not conditions or discussion of what to do if the guide does not cover the task, so it is clear context without exclusions.

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