Skip to main content
Glama

Get my Acubic account

acubic_get_account
Read-onlyIdempotent

Returns the signed-in person's plan, allowance used and when it resets, live-portfolio limits, language, experience level, and a plan comparison with an upgrade link. It does not return the email, payment or broker details. For live holdings use acubic_get_portfolio.

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

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.

Output Schema

NameRequiredDescriptionDefault
liveNo
planNo
errorNo
quotasNo
accountNo
upgradeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the safety profile is settled. The description adds genuinely non-redundant behavior: the exact payload categories returned and the explicit exclusion of email, payment and broker details, which prevents an agent from calling it hoping to recover sensitive account data. It does not mention auth or freshness of allowance figures, so not a 5.

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?

Three short sentences, front-loaded with the return payload, then the exclusions, then the sibling routing. Every clause carries information an agent would otherwise have to discover by trial.

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?

The tool is a zero-required-parameter read with an output schema, so return-value detail belongs in the schema rather than the prose. The description nonetheless covers what is returned, what is deliberately withheld, and where to go for live holdings — nothing an agent needs in order to call it correctly is missing.

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 parameter (locale, with a fixed enum and a description) is fully documented in-schema. The description mentions 'language' only as a returned field and adds no meaning about how locale affects the response or defaults, so the 100%-coverage baseline of 3 applies.

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?

Specific verb and resource ('Returns the signed-in person's plan, allowance used and when it resets, live-portfolio limits, language, experience level...'), followed by an explicit negative scope for email/payment/broker details. An agent can tell immediately this is the account/plan read tool rather than a portfolio or strategy tool.

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 supplies a concrete routing rule — 'For live holdings use acubic_get_portfolio' — which resolves the most likely confusion among the acubic_get_* siblings. It stops short of a full when/when-not statement (e.g. no guidance on whether this should be called before upgrade-related flows), so it is clear context rather than exhaustive routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources