Skip to main content
Glama

agentView

by de.agentview
OverviewDiscussionsAdmin

Get Account

get_account
Read-onlyIdempotent

Returns the user's account profile: plan and features, personal display limits and remaining quota, accessible display count, organization memberships and points balance. Use for subscription, quota and membership questions. Not for listing displays (use list_displays). Requires content scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
access_tokenNoOptional bearer token; prefer session_request_id.
session_request_idNoSession handle from create_auth_session; pass it on every authenticated call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
nameNo
planNo
emailNo
pointsNo
userIdNo
maxDisplaysNo
planFeaturesNo
organizationsNo
currentDisplaysNo
authenticatedViaNo
organizationCountNo
remainingDisplaysNo
maxPersonalDisplaysNo
currentPersonalDisplaysNo
totalAccessibleDisplaysNo
remainingPersonalDisplaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / session_request_id
      Added value: +{
+  "description": "Session handle from create_auth_session; pass it on every authenticated call.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Optional bearer credential. Prefer passing session_request_id (from create_auth_session) instead; every tool accepts it and the server resolves it to your identity server-side. Use access_token only when you hold an OAuth bearer token and your MCP client cannot send it as an Authorization: Bearer HTTP header automatically."New value: +"Optional bearer token; prefer session_request_id."
  3. Changed23 schema fields changed
    • changedOutput schema / properties / authenticatedVia / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / currentDisplays / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / currentPersonalDisplays / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / email / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / hint / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / maxDisplays / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / maxPersonalDisplays / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / name / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / organizationCount / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / organizations / items / properties / displayCount / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / organizations / items / properties / name / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / organizations / items / properties / orgId / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / organizations / items / properties / role / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / organizations / items / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / organizations / type
      Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
    • changedOutput schema / properties / plan / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / planFeatures / items / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / planFeatures / type
      Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
    • changedOutput schema / properties / points / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / remainingDisplays / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / remainingPersonalDisplays / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / totalAccessibleDisplays / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / userId / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Optional JWT access token for authentication. Pass the token returned by get_auth_session when your MCP client does not send it as an Authorization: Bearer HTTP header automatically."New value: +"Optional bearer credential. Prefer passing session_request_id (from create_auth_session) instead; every tool accepts it and the server resolves it to your identity server-side. Use access_token only when you hold an OAuth bearer token and your MCP client cannot send it as an Authorization: Bearer HTTP header automatically."
  5. Changed4 schema fields changed
    • removedInput schema / properties / access_token / default
      Removed value: -null
    • changedInput schema / properties / access_token / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • removedInput schema / properties / session_request_id
      Removed value: -{
-  "default": null,
-  "description": "Optional session request ID returned by create_auth_session. Pass this instead of access_token for simpler, more reliable authentication — the server resolves the identity server-side.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "authenticatedVia": {
+      "type": "string"
+    },
+    "currentDisplays": {
+      "type": "integer"
+    },
+    "currentPersonalDisplays": {
+      "type": "integer"
+    },
+    "email": {
+      "type": "string"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "maxDisplays": {
+      "type": "integer"
+    },
+    "maxPersonalDisplays": {
+      "type": "integer"
+    },
+    "name": {
+      "type": "string"
+    },
+    "organizationCount": {
+      "type": "integer"
+    },
+    "organizations": {
+      "items": {
+        "properties": {
+          "displayCount": {
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          },
+          "orgId": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "plan": {
+      "type": "string"
+    },
+    "planFeatures": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "points": {
+      "type": "integer"
+    },
+    "remainingDisplays": {
+      "type": "integer"
+    },
+    "remainingPersonalDisplays": {
+      "type": "integer"
+    },
+    "totalAccessibleDisplays": {
+      "type": "integer"
+    },
+    "userId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  6. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds a useful extra behavioral constraint: 'Requires content scope,' which is authentication/permission context not present in the annotations. No contradiction with annotations.

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?

Three sentences, each earning its place: what it returns, when to use it, and the explicit exclusion. The description is front-loaded with the resource and output content, and has no filler.

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 annotations covering the safety profile, an output schema covering return structure, and the description covering scope, usage context, and sibling differentiation, nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100% for both parameters, so the schema already fully documents them. The description adds no parameter-specific meaning beyond noting an auth scope requirement, which is not tied to a specific parameter.

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?

The description names a specific verb ('Returns'), a clear resource ('the user's account profile'), and enumerates the data returned (plan, quota, memberships, points). It also explicitly distinguishes itself from list_displays, so an agent can disambiguate among siblings.

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

Usage Guidelines5/5

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

States exactly when to use it ('for subscription, quota and membership questions') and when not to ('Not for listing displays'), naming the alternative tool. This is explicit, actionable routing guidance.

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

All agentView toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources