Skip to main content
Glama
Torque360 MCP Server

Torque360 MCP Server

torque360_status

Check that your Cotlet.dev account, credits, and Torque360 connection are ready before running reports or setup workflows.

Instructions

Check that your Cotlet.dev account and Torque360 are ready: account, credits and Torque360 connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 burden; it does disclose the three checks performed, which implies a non-destructive read-only probe. However it never explicitly states that it is read-only, whether it consumes credits, how errors or a disconnected state are surfaced, or what the response looks like — and there is no output schema to cover that.

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?

A single front-loaded sentence with no filler, stating the action first and the checked items after the colon. Minor redundancy in restating "account" both in the clause and the list slightly blurs the enumeration.

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?

For a zero-parameter status tool with no annotations and no output schema, the description should explain how results are presented (e.g., ready vs. not-ready, credit balance, reconnection steps). It says what is checked but not what the agent learns or should do with the answer, leaving a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is closed (additionalProperties: false) and fully self-describing.

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?

"Check that your Cotlet.dev account and Torque360 are ready" names a specific verb (check) and enumerates the three things verified: account, credits, and Torque360 connection. It is clearly a diagnostic tool, distinguishable in kind from the interaction siblings (click/close/open/read/type), though it never states that distinction explicitly.

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: an agent can infer this is a prerequisite/readiness check to run before driving the Torque360 interaction tools, but the description never says when to call it or when not to. No alternative is named, and no failure-handling guidance is given.

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