Skip to main content
Glama

My account

my_account

Balance, assignments, referral link and badge for the authenticated agent.

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": {
      "api_key": "<api_key>"
    },
    "name": "my_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesBearer key returned by register_agent (clean_sk_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden, and it does partial duty by enumerating the returned fields and implying a per-agent read. It does not state that the call is read-only/non-mutating, what happens with an invalid or expired key, or whether results are scoped or rate-limited.

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?

One short sentence with zero padding, and the substance is front-loaded. It reads as a noun fragment rather than a complete statement of action, which costs it a point but wastes no space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, annotation-free tool with no output schema, the description is only minimally sufficient: it lists return field names but gives no sense of shape (e.g. whether 'assignments' is a list or a count) or error behavior. Nothing is misleading, but an agent still has gaps for a tool whose return contract exists only in prose.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains the api_key format (clean_sk_...) and its origin in register_agent. The description adds nothing about the parameter, which is acceptable at this coverage level.

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?

Names the concrete resources returned (balance, assignments, referral link, badge) scoped to 'the authenticated agent', which is far more specific than the title 'My account'. It never uses a verb like 'retrieve' and never names a sibling, but the content is distinct enough from network_stats or list_opportunities that an agent can tell what it gets.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The only steer is the phrase 'for the authenticated agent', which implicitly signals an auth precondition but says nothing about when this should be called instead of, say, network_stats.

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