UseMyContext.ai

Your plan and usage

account

Read-only

Report the user's current plan and usage: their tier (Free or Premium), how many projects and how much storage they are using against their limits, their subscription status if any, and where they manage their plan. Use this when the user asks what plan they are on, how much storage or how many projects they have used, or whether they are near a limit. Metadata only - no files, facts, or profile content. This is READ-ONLY: you cannot change the plan or start a purchase; plan and billing changes are done by the user themselves at usemycontext.ai. Read-only; nothing is written, so it is safe to call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`tier`	Yes	The user's effective plan.
`usage`	Yes
`limits`	Yes
`upgradeUrl`	Yes	Where the user manages their plan and billing.
`currentPeriodEnd`	No	The current billing-period end (ms epoch), when known.
`subscriptionStatus`	No	The Stripe subscription status, when the user has a subscription.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 9, 2026

changedOutput schema / properties / usage / properties / storageUsedBytes / description

Previous value: -"Total bytes stored across projects."New value: +"Total bytes stored across projects, or null when the storage read is temporarily unavailable."

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

AddedJul 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description explicitly states it is read-only, cannot change the plan or start a purchase, and nothing is written, so it is safe to call. It also limits itself to metadata, preventing misuse for file/content operations.

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?

The description is front-loaded with the core purpose, then usage triggers, then scope and safety. It is slightly wordy with repeated read-only statements, but every sentence adds meaningful information and no filler exists.

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 parameterless read-only tool with an output schema, the description fully covers what it returns (plan, usage, subscription status), when to use it, and its constraints. Nothing needed to call this tool 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 has zero parametersley; the description inherently covers all parameter semantics since there are none to document. The 100% schema coverage and no-argument API make extra parameter explanation unnecessary.

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 uses a specific verb ('Report') and a clear scope: the user's current plan and usage, including tier, project/storage counts, subscription status, and where to manage the plan. It explicitly distinguishes itself from file/fact/profile tools by stating 'Metadata only - no files, facts, or profile content.'

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?

Provides explicit trigger cases: 'Use this when the user asks what plan they are on, how much storage or how many projects they have used, or whether they are near a limit.' It also clarifies exclusions (no files/facts/profile) and that billing changes are done user-side at usemycontext.ai, effectively telling when not to use it.

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

All UseMyContext.ai tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.