QuantGeeks GEX

Your QuantGeeks connection

quantgeeks_get_account

Read-onlyIdempotent

Without signing in: not available; the call asks the user to sign in. Signed in (free account or plan): your name, plan or 'no plan', when you connected and how to disconnect. Which QuantGeeks account this connection uses: the display name the connection was made for, the plan in desk terms, when it was connected, and how to disconnect. Call it when the user asks to sign in, log in or connect their QuantGeeks account, whose data this is, or whether they are signed in.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`name`	No
`note`	No
`plan`	No
`as_of`	Yes
`access`	Yes
`notice`	Yes
`source`	Yes
`symbol`	Yes
`account`	No
`preview`	Yes
`pro_plan`	No
`signed_in`	Yes
`truncated`	No
`disconnect`	No
`connected_at`	No
`not_included`	No
`how_to_sign_in`	No
`truncated_more`	No
`plan_checked_at`	No
`tools_available`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description does add one genuinely useful behavioral fact beyond that: unsigned users get an auth prompt rather than data, and signed-in free users see 'no plan'. It does not cover rate limits or response shape, and the duplicated payload sentences dilute the added value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The when-to-use clause is helpfully front-loaded at the end, but two sentences restate the same return payload (name/plan/connected-time/disconnect) in different wording, which is pure redundancy. The auth-state framing at the start is effective; the middle is bloated.

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?

An output schema exists, so return values need not be spelled out, and the description still covers the key branch (signed out vs signed in vs no plan) plus disconnect guidance. For a zero-parameter, annotation-covered read, that is close to complete.

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. It correctly implies the call is parameterless by describing behavior as dependent only on sign-in state.

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?

The description makes clear this returns the user's QuantGeeks connection/account state (display name, plan, connection time, disconnect path) rather than market data, which distinguishes it from the data-oriented siblings. It is muddied by stating the same payload twice in slightly different words, and the framing sentence 'Which QuantGeeks account this connection uses' is awkward, so it stops short of a crisp verb+resource statement.

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?

It gives explicit triggers: call it when the user asks to sign in, log in, connect their account, asks whose data this is, or asks whether they are signed in. No alternatives or exclusions are named, and the sibling list contains no comparable account tool, so there is little to route against, but the when-to-use coverage is concrete.

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

All QuantGeeks GEX tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?