activated-ai

my_access

Read-onlyIdempotent

Use this when the user asks about access, subscription, remaining limits, or usage («что мне доступно», «сколько осталось», «моя подписка»). Показывает доступ: подписка, доступные советники, потрачено за месяц, лимиты.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`note`	No
`limits`	Yes
`this_month`	Yes
`subscription`	Yes
`advisors_available`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 12, 2026

addedOutput schema / properties / limits / properties / calls_per_min
```
Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}
```

changedOutput schema / properties / limits / properties / shared_with_web / description

Previous value: -"Часовой и дневной лимиты общие с вебом; в вебе 10 сообщений в минуту."New value: +"Часовой и дневной счётчики общие с вебом; в вебе 10 сообщений в минуту."

changedOutput schema / properties / limits / required

Previous value: -[
-  "messages_per_minute",
-  "messages_per_hour",
-  "messages_per_day",
-  "shared_with_web",
-  "temporary_block_on_exceed"
-]New value: +[
+  "messages_per_minute",
+  "messages_per_hour",
+  "messages_per_day",
+  "shared_with_web",
+  "temporary_block_on_exceed",
+  "calls_per_min"
+]

Changed1 schema field changedOct 5, 2026
- addedOutput schema / properties / subscription / properties / source
```
Added value: +{
+  "enum": [
+    "gift"
+  ],
+  "type": "string"
+}
```

Changed13 schema fields changedSep 27, 2026

changedOutput schema / properties / advisors_available / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

removedOutput schema / properties / limits / properties / calls_per_min
```
Removed value: -{
-  "minimum": 1,
-  "type": "integer"
-}
```
removedOutput schema / properties / limits / properties / consultations_per_day
```
Removed value: -{
-  "minimum": 1,
-  "type": "integer"
-}
```
addedOutput schema / properties / limits / properties / messages_per_day
```
Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}
```
addedOutput schema / properties / limits / properties / messages_per_hour
```
Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}
```
addedOutput schema / properties / limits / properties / messages_per_minute
```
Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}
```

addedOutput schema / properties / limits / properties / shared_with_web

Added value: +{
+  "description": "Часовой и дневной лимиты общие с вебом; в вебе 10 сообщений в минуту.",
+  "type": "boolean"
+}

addedOutput schema / properties / limits / properties / temporary_block_on_exceed
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / limits / required

Previous value: -[
-  "calls_per_min",
-  "consultations_per_day"
-]New value: +[
+  "messages_per_minute",
+  "messages_per_hour",
+  "messages_per_day",
+  "shared_with_web",
+  "temporary_block_on_exceed"
+]

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / subscription / properties / plan_id
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / subscription / required

Previous value: -[
-  "active",
-  "plan",
-  "expires_at"
-]New value: +[
+  "active",
+  "plan",
+  "plan_id",
+  "expires_at"
+]

changedOutput schema / properties / this_month / properties / calls / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```

Changed1 schema field changedAug 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "advisors_available": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "limits": {
+      "additionalProperties": false,
+      "properties": {
+        "calls_per_min": {
+          "minimum": 1,
+          "type": "integer"
+        },
+        "consultations_per_day": {
+          "minimum": 1,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "calls_per_min",
+        "consultations_per_day"
+      ],
+      "type": "object"
+    },
+    "subscription": {
+      "additionalProperties": false,
+      "properties": {
+        "active": {
+          "type": "boolean"
+        },
+        "expires_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "plan": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "active",
+        "plan",
+        "expires_at"
+      ],
+      "type": "object"
+    },
+    "this_month": {
+      "additionalProperties": false,
+      "properties": {
+        "calls": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "tokens": {
+          "minimum": 0,
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "calls",
+        "tokens"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "subscription",
+    "advisors_available",
+    "this_month",
+    "limits"
+  ],
+  "type": "object"
+}

First observedAug 1, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the set of values returned (subscription, advisors, spend, limits), but says nothing about auth requirements or freshness/caching of the usage numbers. With annotations carrying the burden, a 3 is appropriate.

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?

Two sentences, front-loaded with the usage triggers before the payload description, with no filler. The bilingual duplication of trigger phrases is functional (matching user wording) rather than wasteful, though it makes the first sentence dense.

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-parameter read-only tool with a full output schema and rich annotations, the description covers both invocation conditions and expected payload at an adequate level. It could be marginally stronger by noting it summarizes the same data that list_advisors surfaces individually, but nothing needed to call it correctly 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument invocation.

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 resource ('доступ') and enumerates exactly what it reports: subscription, available advisors, monthly spend, and limits. It is clearly distinguishable from siblings like list_advisors or ask_advisor, which manage or query advisors rather than reporting the caller's own account state.

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?

It gives explicit trigger conditions with concrete user phrasings («что мне доступно», «сколько осталось», «моя подписка»), which tells the agent exactly when to reach for it. It stops short of naming a sibling as an alternative or stating exclusions, so it is clear context rather than full when/when-not routing.

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

All activated-ai tools Inspect

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

Need Help?