Skip to main content
Glama
Torque360 MCP Server

Torque360 MCP Server

torque360_read

Reads the current Torque360 page, returning its text plus numbered buttons, links and fields so an AI agent can inspect a report or setup screen before acting.

Instructions

Read the current Torque360 page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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. It discloses the shape of what comes back (text and numbered interactive elements), but says nothing about whether it is read-only, what happens when no page is open, whether the text is truncated, or how the numbering is assigned.

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 front-loaded sentence with the verb, target and return contents, and no filler. It could be slightly tighter about what "numbered" means, but nothing is wasted.

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 simple one-optional-param tool with no output schema, the description should explain the returned page representation, and it does at a high level. It still leaves an agent guessing about failure modes and whether the read is safe or has side effects.

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%, with the single optional `element` parameter already documented as "Read only inside this element." The description does not mention the parameter at all, so the baseline 3 applies — the schema does all the work here.

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 ("Read") and resource ("the current Torque360 page"), and even names the return contents: text plus numbered buttons, links and fields. That distinguishes it from siblings like torque360_click or torque360_type by verb alone, though it never explicitly contrasts them.

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 implied rather than stated: "current page" hints a page must already be open, and the emphasis on numbered elements implies this is the discovery step before click/type. There is no explicit when-to-use or when-not guidance and no named alternative.

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