Skip to main content
Glama
Sign In
quantower-mcp

quantower-mcp

by mattdef
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

État du bridge Quantower

quantower_status
Read-only

Check if QuantowerMcpBridge responds and return platform version, MCP server mode, and active connections. Call first to diagnose connection issues.

Instructions

Vérifie que le bridge QuantowerMcpBridge répond, renvoie la version de la plateforme, le mode du serveur MCP (read_only ou trading) et la liste des connexions actives. À appeler en premier pour diagnostiquer un problème de connexion.

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": "quantower_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true. The description adds substantial context beyond that: it reports platform version, server mode (read_only or trading), and active connections — behaviors and return content not derivable from the annotation. It also hints at the diagnostic role first-call ordering.

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?

Two sentences, front-loaded with the core action and result list, followed by the usage directive. Every clause earns its place; no filler.

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

Completeness5/5

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

With zero parameters and no output schema, the description fully describes what the tool returns (version, mode, connections) and when to call it. Nothing an agent needs to invoke it correctly is missing.

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?

No parameters exist, so baseline is 4. The description correctly implies no input is required; no further parameter semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Vérifie que... répond'), the resource (QuantowerMcpBridge), and enumerates the exact outputs: platform version, MCP server mode (read_only or trading), and active connections. This distinguishes it from siblings like quantower_list_connections, which lists a single resource, whereas this tool is a diagnostic bridge check.

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

Usage Guidelines5/5

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

It explicitly says 'À appeler en premier pour diagnostiquer un problème de connexion' — telling the agent exactly when to use this tool (first, for connection troubleshooting). No alternatives are named, but for a diagnostic entry point that isn't needed.

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

Deploy Server

Other Tools