Skip to main content
Glama

AceRound AI Interview Copilot

get_account

Read-only

The signed-in account: remaining minutes, pass level and expiry, mock interview and prediction credits, Auto Apply credits, and the payment status of the 10 most recent orders. Use it to confirm a purchase made through a purchase link went through. (Requires the user's sign-in with scope account:read.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the description's job is to add context beyond that, which it does by disclosing the scope requirement (account:read) and bounding the order data to the 10 most recent orders. It does not describe failure behavior when the user is not signed in, but the auth prerequisite and data ceiling are the substantive additions an agent needs.

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 what is returned and followed by the one situation that motivates the call. The parenthetical auth requirement sits at the end where it belongs, and every clause carries information.

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 parameters, no output schema, and annotations covering the safety profile, the description fills the remaining gaps by enumerating the returned data fields and stating the auth scope. An agent has enough to decide whether to call it and what it will get back.

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 no parameter semantics burden and the baseline is 4. The description correctly implies no inputs are needed by framing the call purely in terms of the signed-in account.

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 uses a specific verb and resource ('The signed-in account') and enumerates the exact contents: remaining minutes, pass level and expiry, mock interview and prediction credits, Auto Apply credits, and recent order payment status. This clearly separates it from narrower siblings like get_auto_apply_quota, though it never names that overlap explicitly, so the differentiation is left partly to inference.

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 a concrete triggering scenario: 'Use it to confirm a purchase made through a purchase link went through.' That is a clear use context, but there are no exclusions or explicit alternatives, even though siblings such as get_purchase_link, get_gift_code_info, and get_auto_apply_quota cover adjacent purchase/credit questions an agent might otherwise route here.

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