Skip to main content
Glama

Sitey — free subdomains

by my.sitey
OverviewDiscussionsAdmin

list_subdomains

List all subdomains you own. Returns subdomain name, domain, record type, value, and creation date. Filtered by your API key, or by the owner_token you pass, or — for records made before tokens existed — by your IP address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
owner_tokenNoThe owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creating without one mints a new one and returns it once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / owner_token
      Added value: +{
+  "description": "The owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creating without one mints a new one and returns it once.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains what is returned, the ownership filtering modes, and the legacy token behavior. It doesn't cover edge cases like pagination or error behavior, but for a simple list tool the provided behavior is well disclosed.

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 sentences, both purposeful and front-loaded. The first states the core action and scope; the second covers return fields and filtering logic. No filler or redundant wording.

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 simple list tool with one optional parameter and no output schema, the description is complete: it names the output fields, explains ownership scoping, and covers the legacy token case. An agent has enough information to invoke it correctly.

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?

The schema covers the only parameter, owner_token, with detailed guidance on omission conditions. The description adds context about filtering by API key and IP, but largely restates what the schema already communicates, so it doesn't meaningfully increase understanding beyond the baseline.

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 and resource: 'List all subdomains you own.' It clearly differentiates from sibling list_domains by focusing on subdomains, and from create/delete/update tools by being a read/list operation. The scope is unambiguous.

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?

The description provides clear context for when to use the tool: when you want to list subdomains you own, filtered by API key, owner token, or legacy IP ownership. It doesn't explicitly mention alternatives or when not to use it, but the context is strong enough that an agent can select it appropriately among the siblings.

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

All Sitey — free subdomains 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