Skip to main content
Glama

notolens

by com.notolens
OverviewDiscussionsAdmin

Get account

get_account
Read-only

Get the account context for this connection: the organization this token operates on, its subscription plan, limits and current usage, the signed-in user's timezone and digest notification settings, and whether this connection has write access (write_access). It confirms which organization the connection acts on. A null plan means the organization has no paid subscription; pricing_url is the public page that describes the plans. On a read-only connection, new_monitor_url and settings_url are the handoff links for setup and preferences.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planYes
usageYes
limitsYesPlan limits: monitors counts every monitor in the organization, paused ones included; domains, trademarks and apps count the active assets of each type on one monitor. Archived assets free their slot. usage holds the counts these limits apply to.
timezoneYesThe signed-in user's IANA timezone, used for dashboard timestamps and the digest send hour. Null falls back to UTC for the digest.
pricing_urlYes
organizationYes
settings_urlYes
write_accessYesWhether this connection has write access: the mcp:write scope, or an API token with write access. When false, write tools fail until the user reconnects the client and approves the write permission, or switches to an API token with write access.
notificationsYesThe signed-in user's digest settings: daily or off, plus the send hour in the user's timezone. Null when the connection has no user.
new_monitor_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / timezone
      Added value: +{
+  "description": "The signed-in user's IANA timezone, used for dashboard timestamps and the digest send hour. Null falls back to UTC for the digest.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • removedOutput schema / properties / user
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": false,
-      "properties": {
-        "email": {
-          "type": "string"
-        },
-        "name": {
-          "type": "string"
-        },
-        "timezone": {
-          "description": "The user's IANA timezone, used for dashboard timestamps and the digest send hour. Null falls back to UTC for the digest.",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "name",
-        "email",
-        "timezone"
-      ],
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • changedOutput schema / required
      Previous value: -[
-  "user",
-  "organization",
-  "plan",
-  "limits",
-  "usage",
-  "notifications",
-  "write_access",
-  "new_monitor_url",
-  "pricing_url",
-  "settings_url"
-]New value: +[
+  "timezone",
+  "organization",
+  "plan",
+  "limits",
+  "usage",
+  "notifications",
+  "write_access",
+  "new_monitor_url",
+  "pricing_url",
+  "settings_url"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / write_access / description
      Previous value: -"Whether this connection has write access: the mcp:write scope, or an agent token with write access. When false, write tools fail until the user reconnects the client and approves the write permission, or switches to an agent token with write access."New value: +"Whether this connection has write access: the mcp:write scope, or an API token with write access. When false, write tools fail until the user reconnects the client and approves the write permission, or switches to an API token with write access."
  3. Changed1 schema field changed
    • changedOutput schema / properties / write_access / description
      Previous value: -"Whether this connection holds the mcp:write scope. When false, write tools fail until the user reconnects the client and approves the write permission."New value: +"Whether this connection has write access: the mcp:write scope, or an agent token with write access. When false, write tools fail until the user reconnects the client and approves the write permission, or switches to an agent token with write access."
  4. Changed5 schema fields changed
    • removedOutput schema / properties / billing_url
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / organization / properties / id
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / organization / required
      Previous value: -[
-  "id",
-  "name"
-]New value: +[
+  "name"
+]
    • addedOutput schema / properties / pricing_url
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "user",
-  "organization",
-  "plan",
-  "limits",
-  "usage",
-  "notifications",
-  "write_access",
-  "new_monitor_url",
-  "billing_url",
-  "settings_url"
-]New value: +[
+  "user",
+  "organization",
+  "plan",
+  "limits",
+  "usage",
+  "notifications",
+  "write_access",
+  "new_monitor_url",
+  "pricing_url",
+  "settings_url"
+]
  5. Changed3 schema fields changed
    • addedOutput schema / properties / limits / description
      Added value: +"Plan limits: monitors counts every monitor in the organization, paused ones included; domains, trademarks and apps count the active assets of each type on one monitor. Archived assets free their slot. usage holds the counts these limits apply to."
    • addedOutput schema / properties / usage
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "active_monitors": {
+      "description": "Active monitors; resuming a paused monitor needs this below limits.monitors.",
+      "type": "number"
+    },
+    "by_monitor": {
+      "description": "Active assets of each type per monitor; add_asset needs the count for its type below the matching limit.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "apps": {
+            "type": "number"
+          },
+          "domains": {
+            "type": "number"
+          },
+          "monitor_id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "active",
+              "paused"
+            ],
+            "type": "string"
+          },
+          "trademarks": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "monitor_id",
+          "name",
+          "status",
+          "domains",
+          "trademarks",
+          "apps"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "monitors": {
+      "description": "All monitors, paused ones included; create_monitor needs this below limits.monitors.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "monitors",
+    "active_monitors",
+    "by_monitor"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "user",
-  "organization",
-  "plan",
-  "limits",
-  "notifications",
-  "write_access",
-  "new_monitor_url",
-  "billing_url",
-  "settings_url"
-]New value: +[
+  "user",
+  "organization",
+  "plan",
+  "limits",
+  "usage",
+  "notifications",
+  "write_access",
+  "new_monitor_url",
+  "billing_url",
+  "settings_url"
+]
  6. Changed1 schema field changed
    • changedOutput schema / properties / write_access / description
      Previous value: -"Whether this connection holds the mcp:write scope. When false, write tools fail; reconnect with the write permission approved."New value: +"Whether this connection holds the mcp:write scope. When false, write tools fail until the user reconnects the client and approves the write permission."
  7. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), yet the description still adds real behavioral context: write_access discloses whether the connection can mutate, null plan signals no paid subscription, and read-only connections get handoff links instead of in-app actions. That last point is genuine behavior an agent could not derive from annotations or schema.

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?

Four sentences, front-loaded with the resource and its payload. The sentence 'It confirms which organization the connection acts on' partially restates the opening clause, which is the one slightly wasteful line; the rest earns its place.

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?

An output schema exists, so return structure need not be spelled out, yet the description still flags the non-obvious field semantics (null plan, write_access, read-only handoff URLs) that an agent would otherwise misread. For a parameterless read tool, nothing needed for correct invocation is missing.

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 input parameters, so the baseline is 4. The description spends its words on return-field semantics (null plan, pricing_url, write_access, the two handoff URLs), which is useful but technically output rather than parameter meaning.

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 ('Get the account context for this connection') and enumerates exactly what is returned: organization, plan, limits, usage, timezone, digest settings, write_access. No sibling tool touches account/connection state, so an agent can route to this immediately without opening the schema.

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?

Usage is only implied by the clause 'It confirms which organization the connection acts on' — an agent can infer this is the call to make before acting on an org-scoped operation, but there is no explicit when-to-use, no exclusions, and no named alternative. Adequate but leaves the trigger to inference.

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

All notolens 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