Gajo URL Shortener

Check plan and quota

get_usage

Read-only

Shows your plan and quota: links created and remaining this month, maximum link lifetime, and API requests per minute. Call it before creating many links or after a monthly-limit error; the allowance resets on the 1st of each month (UTC).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	Yes
`totalUrls`	No
`totalClicks`	No
`urlsRemaining`	Yes
`urlsMonthlyLimit`	Yes
`requestsPerMinute`	Yes
`maxLinkLifetimeDays`	No	null when links never expire.
`urlsCreatedThisMonth`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "maxLinkLifetimeDays": {
+      "description": "null when links never expire.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "plan": {
+      "type": "string"
+    },
+    "requestsPerMinute": {
+      "type": "integer"
+    },
+    "totalClicks": {
+      "type": "integer"
+    },
+    "totalUrls": {
+      "type": "integer"
+    },
+    "urlsCreatedThisMonth": {
+      "type": "integer"
+    },
+    "urlsMonthlyLimit": {
+      "type": "integer"
+    },
+    "urlsRemaining": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "plan",
+    "urlsCreatedThisMonth",
+    "urlsMonthlyLimit",
+    "urlsRemaining",
+    "requestsPerMinute"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

A4.5/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. The description adds genuine behavioral context beyond that: the allowance resets on the 1st of each month (UTC) and per-minute API request limits exist. It does not discuss caching or failure modes, but the reset cadence is a meaningful addition.

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?

Two tightly written sentences: the return contents are front-loaded, followed by the call triggers and the reset caveat. Every clause carries information and nothing is redundant.

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-value shape need not be restated. Combined with the annotations covering the safety profile, the description supplies everything an agent needs: what it reports, when to call it, and the monthly reset behavior.

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 clarify; the baseline for a parameterless tool is 4. No parameter gaps exist to compensate for.

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 states a specific verb ('Shows') and resource ('your plan and quota') and enumerates exactly what is returned: links created and remaining this month, maximum link lifetime, and API requests per minute. This clearly separates it from the URL-management siblings (shorten_url, list_urls, get_url_stats), none of which report account-level plan/limit 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: 'Call it before creating many links or after a monthly-limit error.' That is clear when-to-use guidance tied to a concrete workflow. It stops short of naming alternatives or an explicit when-not case, so it sits just below the top band.

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

All Gajo URL Shortener tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?