Skip to main content
Glama

Research allowance and account status

get_account_status
Read-onlyIdempotent

Check how many standard research requests the connected account has left, including signup or purchased requests and subscription allowance. Use for credits, balance, remaining free searches or payment/account questions. Free even when no research allowance remains; does not run research or consume credits. Return the account and research plans links when needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get_account_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesUser's research goal in one short sentence (max 300 characters); include relevant ticker and topic. Exclude names, contact/account/portfolio details, credentials and source text.
llm_modelYesYour model identifier, if known (e.g. gpt-6); otherwise leave unknown. Exclude credentials and private deployment names.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new operational facts: calls are free even when no allowance remains, they never consume credits, and the response can include account and research plans links. It does not discuss error states (e.g., what happens with an unconnected account), which is the only notable omission beyond the annotation coverage.

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 cost and no-side-effect guarantee is front-loaded where an agent needs it, and each sentence carries usable information. There is mild overlap between 'signup or purchased requests and subscription allowance' and 'credits, balance, remaining free searches', which could be tightened but does not obscure the meaning.

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?

For a read-only status tool with full schema coverage and an existing output schema, the description covers the essential unknowns: cost, absence of side effects, and what kinds of allowance are counted. The return values need not be explained, though a note on behavior when no account is connected would round it out.

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?

The description says nothing about the three parameters (context, llm_model, conversation_id). With schema description coverage at 100%, the schema already carries the full burden, including the detailed conversation_id persistence rule, so the baseline of 3 applies — the description neither helps nor harms here.

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?

States a specific verb and resource (check remaining standard research requests for the connected account) and enumerates what the number is composed of: signup/purchased requests plus subscription allowance. It also draws a hard boundary against the sibling research tools by saying it 'does not run research or consume credits', so an agent can separate it from get_brief, get_research_sample, and the rest without opening any schema.

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?

Gives concrete triggers — credits, balance, remaining free searches, payment/account questions — which is clear when-to-use guidance. It does not name a specific sibling as the alternative for research execution, relying instead on the negative statement that it does not run research, so it stops just short of explicit 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.