Skip to main content
Glama

get_my_usage

Read-onlyIdempotent

Your current TipRanks MCP usage against the monthly tool-call quota.

Reports calls used this calendar month, your limit, how many remain, your
plan tier, and when the quota resets (UTC). Handy to check before running a
large batch of calls. This call is free — it never counts against the quota.

What counts: every tool call is metered once whether or not it returns data,
so an unrecognised ticker or an invalid argument costs the same as a
successful call. The connection handshake (initialize, tools/list and the
other discovery calls) is never metered, and neither is this tool.

Calls refused for being over the limit are refunded on both ladders, so
`used` settles at the cap rather than climbing while a client retries. It
can still read higher than `limit` when the ceiling FELL mid-month — a
complimentary grant expiring or being revoked, or a paid MCP subscription
lapsing — and there it is the count of calls genuinely served before the
cap dropped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that this call is free and never counts against the quota, that all other metered calls count even on failure, that handshake/discovery calls are unmetered, and that refused calls are refunded. It also explains the edge case where `used` can exceed `limit` when the cap falls mid-month.

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?

The description is front-loaded with the core summary and then organized into clear, purposeful paragraphs. It is longer than strictly necessary, but each paragraph adds meaningful behavioral detail that helps an agent avoid misinterpreting quota edge cases.

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 no output schema, the description covers the returned fields: calls used, limit, remaining calls, plan tier, and reset time. It also covers free-call status, metering rules, and edge-case behavior, making it fully self-sufficient for correct invocation and interpretation.

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 has zero parameters and the schema coverage is trivially 100%, so the description does not need to explain parameters. It still adds relevant context by clarifying that invoking this tool has no metering side effects.

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 the tool's specific function: reporting the current TipRanks MCP usage against the monthly tool-call quota. It clearly distinguishes itself from the many data-retrieval siblings by focusing on quota state rather than market data.

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?

The description explicitly recommends checking usage before running a large batch of calls, giving clear contextual guidance. It does not name alternatives or exclusion cases, but none are needed since no sibling tool serves this purpose.

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.

TDQS

A3.8/5.0
Disambiguation3/5

Many tools have overlapping purposes, e.g. get_etf_analysis vs get_etf_forecast both provide ETF analyst consensus, get_etf_holdings vs get_etf_top_stocks both list constituents, and get_portfolio_overview vs get_portfolio_performance both return returns/performance. The detailed descriptions help, but the sheer number of similar tools creates ambiguity in selection.

Naming Consistency4/5

The set is largely consistent with a 'get_' prefix and descriptive nouns (get_stock_quotes, get_crypto_quote, get_dividend_history). Minor deviations include 'list_my_portfolios' instead of 'get_my_portfolios' and singular/plural variants like get_all_commodities_quotes vs get_commodity_quote, but the pattern remains predictable.

Tool Count1/5

With 71 tools, the count far exceeds the 50+ threshold described as an extreme mismatch. Even though the server covers a broad financial domain, such a large surface is overwhelming for an agent and includes many redundant or highly specific tools that could be consolidated.

Completeness5/5

The tool set provides comprehensive coverage of TipRanks data: quotes and historical data for all major asset classes, news, earnings and economic calendars, analyst and sentiment data, financial statements, technical analysis, options, portfolios, and screeners. There are no obvious dead ends for typical financial research tasks.

Resources