Surli MCP

get_account_limits

Read-onlyIdempotent

Check current user tariff plan and available short link limits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`plan`	Yes	Current account tariff plan (e.g. limited, unlimited)
`used`	Yes	Number of short links used in the current plan period
`limit`	Yes	Total short link quota for the plan period (-1 = unlimited)
`alias_max`	No	Maximum custom alias updates allowed (0 if not supported by plan)
`remaining`	Yes	Number of short links remaining (-1 = unlimited)
`upgrade_url`	No	URL to upgrade the tariff plan
`user_message`	No	Human-readable summary of plan usage

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "alias_max": {
+      "description": "Maximum custom alias updates allowed (0 if not supported by plan)",
+      "type": "integer"
+    },
+    "limit": {
+      "description": "Total short link quota for the plan period (-1 = unlimited)",
+      "type": "integer"
+    },
+    "plan": {
+      "description": "Current account tariff plan (e.g. limited, unlimited)",
+      "type": "string"
+    },
+    "remaining": {
+      "description": "Number of short links remaining (-1 = unlimited)",
+      "type": "integer"
+    },
+    "upgrade_url": {
+      "description": "URL to upgrade the tariff plan",
+      "type": "string"
+    },
+    "used": {
+      "description": "Number of short links used in the current plan period",
+      "type": "integer"
+    },
+    "user_message": {
+      "description": "Human-readable summary of plan usage",
+      "type": "string"
+    }
+  },
+  "required": [
+    "plan",
+    "limit",
+    "used",
+    "remaining"
+  ],
+  "type": "object"
+}

First observedSep 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds specific details about what is checked (tariff plan and short link limits), which enriches the behavioral context beyond the annotations.

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?

The description is a single, front-loaded sentence with no redundant words. It states the verb first and the precise resources, making it directly actionable.

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?

With an existing output schema, no parameters, and a clear description of what is checked, the tool is complete. An agent can correctly invoke it without additional context.

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?

There are no parameters, so schema coverage is trivially 100%. The baseline for 0-parameter tools is 4. The description adds no parameter info (none needed) and remains sufficient.

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 ('Check') and clearly identifies the resources ('current user tariff plan' and 'available short link limits'). This distinguishes it from siblings like create_short_link or update_alias, which are action-oriented. An agent can immediately understand the tool's scope.

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?

The description implies a query for checking limits but does not explicitly state when to use it versus alternatives. It does not mention exclusions or recommend using it before link creation. While context suggests it, explicit guidance is missing.

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

All Surli MCP 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?