Skip to main content
Glama

MiniURL

by io.github.addychang
OverviewDiscussionsAdmin

MiniURL add_domain

add_domain
Destructive

Request a custom domain to be connected to MiniURL. Agent domain changes require human approval by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesAn apex domain such as example.com or subdomain such as links.example.com. New domains use A + ownership TXT records and automatic HTTPS on the server.
approval_idNo
approval_tokenNoLegacy compatibility field; normally omit it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
metaNo
errorNo
successYes
approvalNo
retryableNo
request_idYes
retry_afterNo
next_actionsNo
required_scopeNo
user_action_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"A custom hostname such as links.example.com."New value: +"An apex domain such as example.com or subdomain such as links.example.com. New domains use A + ownership TXT records and automatic HTTPS on the server."
  2. Changed1 schema field changed
    • changedOutput schema / properties / data / type
      Previous value: -[
-  "object",
-  "array",
-  "null"
-]New value: +[
+  "object",
+  "array",
+  "string",
+  "number",
+  "boolean",
+  "null"
+]
  3. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / approval_token / description
      Added value: +"Legacy compatibility field; normally omit it."
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedOutput schema / properties / data / additionalProperties
      Added value: +true
    • changedOutput schema / properties / data / type
      Previous value: -[
-  "object",
-  "array",
-  "string",
-  "number",
-  "boolean",
-  "null"
-]New value: +[
+  "object",
+  "array",
+  "null"
+]
    • changedOutput schema / properties / error / oneOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "required_scope": {
-        "type": "string"
-      },
-      "retry_after": {
-        "minimum": 0,
-        "type": "integer"
-      },
-      "retryable": {
-        "type": "boolean"
-      },
-      "user_action_required": {
-        "type": "boolean"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "required_scope": {
+        "type": "string"
+      },
+      "retry_after": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "retryable": {
+        "type": "boolean"
+      },
+      "user_action_required": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "message",
+      "retryable"
+    ],
+    "type": "object"
+  }
+]
    • addedOutput schema / properties / request_id / minLength
      Added value: +8
    • changedOutput schema / required
      Previous value: -[
-  "request_id"
-]New value: +[
+  "success",
+  "request_id"
+]
  4. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so safety is partly covered. The description adds the non-obvious behavioral fact that agent-initiated changes require human approval, which is genuinely useful. But it doesn't explain what 'request' means operationally, whether the domain is immediately live, or how approval_id/token interact with that flow.

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 front-loaded sentences with zero filler: the action first, then the critical approval constraint. Nothing can be cut without losing signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 values need not be described. But for a mutation tool with destructiveHint=true, the description under-explains the approval flow (where approval_id comes from, what happens if it's absent), leaving a meaningful operational gap.

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 coverage is 67%, with 'domain' richly documented in-schema and 'approval_token' annotated as legacy/omit. The description adds no parameter-level detail, leaving 'approval_id' undocumented in both schema and prose, so it neither compensates nor adds value here.

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?

States a specific verb (add/request) and resource (custom domain) tied to MiniURL, so the agent can tell it apart from list_domains, delete_domain, and verify_domain. It stops short of explicitly contrasting with the closest sibling (verify_domain), which would push it to a 5.

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 sentence 'Agent domain changes require human approval by default' implies a prerequisite workflow before calling, which is real usage context. However, it never says when to choose this over alternatives, nor what to do when approval is needed, so usage is only implied.

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

All MiniURL toolsInspect
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