Skip to main content
Glama

Get account

get_account
Read-only

The connected workspace, its credit balance, today's agent spend and the agent limits.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered and the description's remaining job is small. It adds useful scope context by saying this is the *connected* workspace (no ID argument, single fixed target) and names the exact data returned, but says nothing about freshness, rate limits, or failure modes.

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?

A single short sentence with no filler, and the most useful item (workspace) is front-loaded. It is a fragment rather than a complete statement of action, which costs it polish but not clarity.

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 zero-argument read with a full output schema and complete safety annotations, the description needs to convey only what category of data comes back, and it does so precisely. Nothing required to invoke it correctly is missing, though a note on when the snapshot is refreshed 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 tool takes zero parameters, so there is no parameter meaning for the description to add beyond the schema. The description correctly implies no argument is needed because the 'connected workspace' is implicit, which is the only semantic point available here.

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 enumerates the exact contents returned: workspace identity, credit balance, today's agent spend, and agent limits. That makes the resource specific enough to distinguish it from siblings like switch_workspace or list_models, though it is a bare noun phrase with no verb stating the retrieval action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The listed fields imply when an agent would call this (checking credit balance, spend, or limits before a costly generation), but the description never states a trigger, prerequisite, or relationship to alternatives such as estimate_cost. Usage is only inferable from the returned-content list.

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