Skip to main content
Glama
Sign In

rentadomain

by sh.rentadomain
OverviewDiscussionsAdmin

Search listed names

search_names
Read-onlyIdempotent

Lists the domain names rentadomain.sh has for rent right now, each with its monthly price and term menu; call it first, or whenever the user wants a domain and has not named one. Pass the user's own words as the query: names are matched on their host and keywords and ranked by how many words they match, and a miss returns the names closest in spelling.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many names to return, 1 to 50.
queryNoThe person's words for the name they want (a sentence works) or a piece of a host; empty or absent lists every name.

Output Schema

NameRequiredDescriptionDefault
namesYes
queryYes
totalYes
closestYes
closest_whyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Text the host must contain; empty or absent lists every name."New value: +"The person's words for the name they want (a sentence works) or a piece of a host; empty or absent lists every name."
    • addedOutput schema / properties / closest
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "host": {
+        "type": "string"
+      },
+      "monthly": {
+        "type": "string"
+      },
+      "monthly_cents": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "rent_url": {
+        "type": "string"
+      },
+      "term_menu": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "monthly": {
+              "type": "string"
+            },
+            "monthly_cents": {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            },
+            "months": {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            }
+          },
+          "required": [
+            "months",
+            "monthly_cents",
+            "monthly"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "host",
+      "monthly_cents",
+      "monthly",
+      "term_menu",
+      "url",
+      "rent_url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / closest_why
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / names / items / properties / matched
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / names / items / required
      Previous value: -[
-  "host",
-  "monthly_cents",
-  "monthly",
-  "term_menu",
-  "url",
-  "rent_url"
-]New value: +[
+  "host",
+  "monthly_cents",
+  "monthly",
+  "term_menu",
+  "url",
+  "rent_url",
+  "matched"
+]
    • changedOutput schema / required
      Previous value: -[
-  "query",
-  "total",
-  "names"
-]New value: +[
+  "query",
+  "total",
+  "names",
+  "closest",
+  "closest_why"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and a closed catalog, so safety needs no restating. The description adds genuinely new behavior: matching on host and keywords, ranking by count of matched words, and a spelling-proximity fallback on a miss, which tells the agent how to interpret weak results. It stops short of describing result shape or pagination, but an output schema exists.

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 tight sentences with the purpose and result contents front-loaded before the call-order rule and the retrieval semantics. Every clause carries distinct information and nothing is repeated from the schema or annotations.

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 two-parameter, read-only catalog search with an output schema, the definition covers purpose, ordering rule, result contents, and fallback behavior. An agent has everything needed to call it correctly and interpret a poor match.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns a bump by instructing 'Pass the user's own words as the query' – a non-obvious nuance telling the agent not to reformat into keywords and that a full sentence is acceptable. That meaning is not present in the schema, which only says 'a sentence works'.

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 ('Lists the domain names rentadomain.sh has for rent right now') plus what each result carries (monthly price, term menu). That distinguishes it from get_name and get_rent_status, which operate on a specific named domain rather than a catalog listing.

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?

Gives an explicit default-first rule ('call it first') and a precise trigger ('whenever the user wants a domain and has not named one'), which implicitly routes already-named lookups to the sibling tools. No inference is needed to decide when to call it.

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

All rentadomain 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