dochost-mcp

Get my dochost account

get_account

Read-only

Get your plan, page-quota usage, entitlement flags (size cap, custom slug, password, branding), and the primary host new links publish on. Call before publishing so you know your limits up front. The primary host is chosen in the dashboard (manageDomainsUrl), not through this API.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`plan`	Yes
`password`	No
`analytics`	No
`pageQuota`	No
`pagesUsed`	No
`sizeCapMb`	No
`customSlug`	No
`noBranding`	No
`primaryHost`	No	Host new links publish on: a custom domain, `{sub}.dochost.co`, or `dochost.co/d`.
`pagesRemaining`	No
`permanentLinks`	No
`manageDomainsUrl`	No	Dashboard page where the user adds domains and picks the primary one. Send them here to change it.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedSep 6, 2026

addedOutput schema / properties / manageDomainsUrl

Added value: +{
+  "description": "Dashboard page where the user adds domains and picks the primary one. Send them here to change it.",
+  "type": "string"
+}

addedOutput schema / properties / primaryHost

Added value: +{
+  "description": "Host new links publish on: a custom domain, `{sub}.dochost.co`, or `dochost.co/d`.",
+  "type": "string"
+}

Changed1 schema field changedJun 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "analytics": {
+      "enum": [
+        "none",
+        "totals",
+        "full"
+      ],
+      "type": "string"
+    },
+    "customSlug": {
+      "type": "boolean"
+    },
+    "noBranding": {
+      "type": "boolean"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "pageQuota": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "pagesRemaining": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "pagesUsed": {
+      "type": "integer"
+    },
+    "password": {
+      "type": "boolean"
+    },
+    "permanentLinks": {
+      "type": "boolean"
+    },
+    "plan": {
+      "enum": [
+        "free",
+        "pro",
+        "max"
+      ],
+      "type": "string"
+    },
+    "sizeCapMb": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "ok",
+    "plan"
+  ],
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare this as safe and read-only, and the description adds useful behavioral context: it reports usage/quota information, includes entitlement flags, and clarifies that the primary host cannot be changed via the API. No contradiction with 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?

Three sentences with no filler: the return contents are front-loaded, the usage timing follows, and the dashboard caveat closes. Every sentence earns its place.

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?

For a zero-parameter read-only tool with an output schema, the description fully covers what the tool does, when to call it, and an important limitation. The sibling tools and annotations further contextualize it adequately.

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 has no parameters, so the description cannot add parameter-level meaning beyond the schema. The baseline of 4 applies because the schema coverage is complete and no parameter ambiguity exists.

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?

States a specific verb and resource — 'Get your dochost account' — and enumerates exactly what is returned: plan, page-quota usage, entitlement flags, and primary host. This clearly distinguishes it from the page-level sibling tools like get_page and list_my_pages.

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?

Explicitly advises calling 'before publishing' so the agent knows limits up front, tying the tool to the publish workflow. It also spells out a boundary: the primary host is configured in the dashboard and 'not through this API', preventing misuse.

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

All dochost-mcp tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.