Skip to main content
Glama

短.在线

by xn--3ds443g.xn--s7y
OverviewDiscussionsAdmin

Connect account · 浏览器注册入口（短.在线）

begin_registration

客户端无法启动 OAuth 时的后备入口。返回浏览器注册链接。本工具不创建账户，不接收密码，也不代用户同意条款。 Fallback when the client cannot start OAuth. Returns a browser registration link. This tool does not create an account, accept a password, or accept terms for the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoBrowser signup page language. Does not accept email, password, or acceptance. API language preference. Canonical values: en and zh-CN. Documented aliases normalized to the canonical value: zh-cn, zh-Hans, zh-hans, zh_Hans, zh_hans. Traditional Chinese is not supported. EN, ZH-CN, and bare zh are rejected. Omitted or blank defaults to en. This preference does not rewrite URL bytes, translate parameter names, or use the caller's location. Website routes stay /zh-cn.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / oneOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "expires_at": {
+        "type": "string"
+      },
+      "ok": {
+        "const": true,
+        "type": "boolean"
+      },
+      "request_id": {
+        "type": "string"
+      },
+      "resume_token": {
+        "type": "string"
+      },
+      "signup_url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "ok",
+      "request_id",
+      "signup_url",
+      "expires_at",
+      "resume_token"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "error": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "ok": {
+        "const": false,
+        "type": "boolean"
+      },
+      "request_id": {
+        "type": "string"
+      },
+      "retryable": {
+        "type": "boolean"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "ok",
+      "request_id",
+      "error",
+      "code",
+      "message",
+      "type",
+      "title",
+      "retryable"
+    ],
+    "type": "object"
+  }
+]
    • removedOutput schema / properties
      Removed value: -{
-  "code": {
-    "type": "string"
-  },
-  "error": {
-    "type": "string"
-  },
-  "expires_at": {
-    "type": "string"
-  },
-  "message": {
-    "type": "string"
-  },
-  "ok": {
-    "type": "boolean"
-  },
-  "request_id": {
-    "type": "string"
-  },
-  "resume_token": {
-    "type": "string"
-  },
-  "retryable": {
-    "type": "boolean"
-  },
-  "signup_url": {
-    "type": "string"
-  },
-  "title": {
-    "type": "string"
-  },
-  "type": {
-    "type": "string"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "ok"
-]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / title
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / type
      Added value: +{
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"Browser signup language. Does not accept email, password, or acceptance."New value: +"Browser signup page language. Does not accept email, password, or acceptance. API language preference. Canonical values: en and zh-CN. Documented aliases normalized to the canonical value: zh-cn, zh-Hans, zh-hans, zh_Hans, zh_hans. Traditional Chinese is not supported. EN, ZH-CN, and bare zh are rejected. Omitted or blank defaults to en. This preference does not rewrite URL bytes, translate parameter names, or use the caller's location. Website routes stay /zh-cn."
    • changedInput schema / properties / locale / enum
      Previous value: -[
-  "en",
-  "zh-CN"
-]New value: +[
+  "en",
+  "zh-CN",
+  "zh-cn",
+  "zh-Hans",
+  "zh-hans",
+  "zh_Hans",
+  "zh_hans"
+]
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "locale": "en"
+  },
+  {
+    "locale": "zh-CN"
+  }
+]
  5. Added

TDQS

A4.1/5.0
Behavior3/5

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

With annotations declaring readOnlyHint=false, idempotentHint=false, and destructiveHint=false, the description adds valuable clarification that it does not create an account, accept a password, or accept terms. However, it does not explain the non-read-only nature (e.g., whether it starts a session or changes any state), leaving a gap between the annotation and the described behavior.

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 purpose and key caveats. It is somewhat longer due to full bilingual duplication, but each language block is concise and every sentence contributes useful information.

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?

Given the low complexity (one optional parameter), the presence of an output schema, and existing annotations, the description covers purpose, usage condition, and behavioral boundaries well. It could be slightly more complete by addressing the non-read-only annotation or parameter usage, but overall it is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single locale parameter is fully documented in the schema, including aliases, normalization, and defaults. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 applies.

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 purpose: a fallback entry point that returns a browser registration link when the client cannot start OAuth. It clearly distinguishes this tool from the unrelated shortener siblings and avoids tautology.

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?

It explicitly names the triggering condition ('when the client cannot start OAuth') and frames the tool as a fallback. No alternative registration tool exists among siblings, so no further routing guidance is needed.

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

All 短.在线 toolsInspect
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