GimmeText

Get usage

get_usage

Read-only

Use when the user asks how many minutes they have left, or after an out-of-minutes error. Anyone, including free accounts, can add a one-time 5-hour pack for $10 at upgrade_url.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	Yes	Plan id, e.g. free, starter, pro or power (more may be added).
`period_end`	No	ISO 8601 UTC end of the current period, or null.
`upgrade_url`	No	Where to add a one-time hour pack or upgrade the plan.
`bonus_seconds`	No	Seconds left in one-time hour packs (used after the monthly seconds).
`monthly_seconds`	No	Seconds included each period.
`remaining_seconds`	Yes	Seconds of transcription left this period.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

changedOutput schema / properties / bonus_seconds / description

Previous value: -"Carried-over top-up seconds."New value: +"Seconds left in one-time hour packs (used after the monthly seconds)."

addedOutput schema / properties / upgrade_url

Added value: +{
+  "description": "Where to add a one-time hour pack or upgrade the plan.",
+  "type": "string"
+}

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "bonus_seconds": {
+      "description": "Carried-over top-up seconds.",
+      "type": "number"
+    },
+    "monthly_seconds": {
+      "description": "Seconds included each period.",
+      "type": "number"
+    },
+    "period_end": {
+      "description": "ISO 8601 UTC end of the current period, or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "plan": {
+      "description": "Plan id, e.g. free, starter, pro or power (more may be added).",
+      "type": "string"
+    },
+    "remaining_seconds": {
+      "description": "Seconds of transcription left this period.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "plan",
+    "remaining_seconds"
+  ],
+  "type": "object"
+}

First observedOct 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered by structured data. The description adds genuinely non-obvious behavior: the result applies to anyone including free accounts, and there is a self-serve remediation path ($10 one-time 5-hour pack via upgrade_url). It does not say whether upgrade_url is a returned field versus an external link, which is the only ambiguity.

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 short sentences, with the primary trigger front-loaded and no filler. The second sentence is somewhat tangential to what the tool does, sitting closer to remediation advice than tool definition, but it earns its place for the out-of-minutes recovery scenario.

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?

Zero required parameters, full schema coverage, an output schema, and annotations covering the read-only profile mean very little needs to be said. The description covers when to call and what to do with the result; only the nature of upgrade_url (returned field vs. static URL) is left slightly underspecified.

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; the baseline of 4 applies. The mention of upgrade_url in the description could be misread as an input, but the schema makes clear no inputs exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the resource clearly – remaining minutes/usage for the account – and the trigger condition makes the outcome unambiguous. It lacks an explicit verb like 'returns' and the second sentence pivots to upsell content, which dilutes focus slightly, but an agent can still tell what this tool yields.

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?

Two concrete invocation triggers are given: the user asking how many minutes are left, and recovery after an out-of-minutes error. No exclusions or alternative tools are named, but none of the siblings (create_upload_link, get_job, get_transcript, list_jobs) overlaps with usage lookup, so there is little to distinguish against.

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

All GimmeText 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?