Skip to main content
Glama

Get account status

amber_get_account_status
Read-onlyIdempotent

Retrieves the authenticated user's subscription status, next billing date, memory counts, and creation date to answer account, billing, or cancellation questions. Read-only.

Instructions

Return the authenticated user's account summary: subscription state, next billing date, memory counts, and account creation date. Use this when the user asks about their account, subscription status, or how many memories they have.

After cancellation, access continues until next_billing_date (the end of the paid period). Once ACCESS ends, memory counts show as null (data is preserved, just not queryable until resubscribed) -- note that is later than subscription_active turning false, because a cancelled subscription keeps access until its paid period ends and reports real counts until then. If deletion_scheduled_at is set, the account is pending permanent deletion -- use amber_cancel_account_deletion to stop it. Read-only -- does not modify any account state. Not rate-limited.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
user_idYesAmber's own id for this account. Stable, and safe to show.
payer_idYesPayPal Payer ID (permanent account identifier).
member_sinceYesWhen the account was created, as an ISO 8601 UTC datetime, not when the current subscription started.
memory_countYesActive memory count. Null once ACCESS has ended, which is not the same as `subscription_active: false`: a cancelled subscription keeps access until its paid period ends, and reports real counts throughout. Data is preserved either way, just not queryable once access ends.
subscription_idYesThe PayPal subscription this account bills through, or null if there has never been one.
migration_lockedYesTrue while Amber is moving this account's database, during which WRITES are refused with `migration_in_progress` and reads keep working. Normally false. If a store was refused, this is how a caller confirms why and that retrying shortly will succeed rather than the request being malformed.
next_billing_dateYesDate when access expires (ISO 8601). When subscription_active is false and this date is in the future, the user still has access until this date but will NOT be charged again (cancelled/no subscription). When subscription_active is true, this is the next billing date. Null if unknown.
subscription_activeYesWhether the account can currently store and search. False does NOT mean data was lost: memories are preserved and become queryable again on resubscribing.
deleted_memory_countYesTrashed memory count, on the same rule as `memory_count`: null once access has ended, not merely when `subscription_active` is false.
deletion_scheduled_atYesISO 8601 date when the account will be permanently deleted, or null if not scheduled. Use `amber_cancel_account_deletion` to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "deleted_memory_count": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Trashed memory count, on the same rule as `memory_count`: null once access has ended, not merely when `subscription_active` is false."
      +    },
      +    "deletion_scheduled_at": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "ISO 8601 date when the account will be permanently deleted, or null if not scheduled. Use `amber_cancel_account_deletion` to cancel."
      +    },
      +    "member_since": {
      +      "description": "When the account was created, as an ISO 8601 UTC datetime, not when the current subscription started.",
      +      "type": "string"
      +    },
      +    "memory_count": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Active memory count. Null once ACCESS has ended, which is not the same as `subscription_active: false`: a cancelled subscription keeps access until its paid period ends, and reports real counts throughout. Data is preserved either way, just not queryable once access ends."
      +    },
      +    "migration_locked": {
      +      "description": "True while Amber is moving this account's database, during which WRITES are refused with `migration_in_progress` and reads keep working. Normally false. If a store was refused, this is how a caller confirms why and that retrying shortly will succeed rather than the request being malformed.",
      +      "type": "boolean"
      +    },
      +    "next_billing_date": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Date when access expires (ISO 8601). When subscription_active is false and this date is in the future, the user still has access until this date but will NOT be charged again (cancelled/no subscription). When subscription_active is true, this is the next billing date. Null if unknown."
      +    },
      +    "payer_id": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "PayPal Payer ID (permanent account identifier)."
      +    },
      +    "subscription_active": {
      +      "description": "Whether the account can currently store and search. False does NOT mean data was lost: memories are preserved and become queryable again on resubscribing.",
      +      "type": "boolean"
      +    },
      +    "subscription_id": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The PayPal subscription this account bills through, or null if there has never been one."
      +    },
      +    "user_id": {
      +      "description": "Amber's own id for this account. Stable, and safe to show.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "user_id",
      +    "payer_id",
      +    "subscription_active",
      +    "subscription_id",
      +    "next_billing_date",
      +    "deletion_scheduled_at",
      +    "migration_locked",
      +    "memory_count",
      +    "deleted_memory_count",
      +    "member_since"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely non-inferable behavior: no rate limiting, memory counts read as null after access lapses while data is preserved, access persists past `subscription_active` until `next_billing_date`, and the meaning of `deletion_scheduled_at`. This is exactly the operational context annotations cannot carry.

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?

Front-loaded with purpose and trigger before the edge-case detail, and the closing 'Read-only... Not rate-limited' tags are efficient. The middle sentence is convoluted and partly restates itself ('note that is later than `subscription_active` turning false, because a cancelled subscription keeps access until its paid period ends and reports real counts until then').

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?

For a zero-param read with an output schema and full annotation coverage, the description covers everything an agent needs: what triggers it, what the returned states mean over the subscription lifecycle, and where to go to reverse a pending deletion. No meaningful gap remains.

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?

Zero parameters, so the baseline is 4. The description instead spends its words on return-field semantics (what `next_billing_date` and null memory counts mean), which is useful even though an output schema exists.

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 ('Return the authenticated user's account summary') and enumerates exactly what comes back: subscription state, next billing date, memory counts, creation date. An agent can immediately distinguish this read-only status snapshot from the sibling mutation tools like amber_manage_subscription or amber_cancel_account_deletion.

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 an explicit trigger ('Use this when the user asks about their account, subscription status, or how many memories they have') and routes one adjacent case away with 'use amber_cancel_account_deletion to stop it'. It does not, however, disambiguate against amber_manage_subscription or amber_cancel_subscription for subscription-related questions, so the routing is partial rather than exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.