Skip to main content
Glama

Scopeweb

by io.scopeweb
OverviewDiscussionsAdmin

list_domains

Read-onlyIdempotent

Use this at the start of any portfolio, renewal or 'what do I own' question, before assuming which names the user holds. List the user's domain inventory: every domain with a verification challenge issued or completed, plus cached liveness, classification, title and expiry. Read-only. Cannot spend money. Includes scan_age_ms so a stale verdict is never mistaken for a fresh one. Use before suggesting the user buy anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainsYes
verified_countNo
unverified_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "domains": {
+      "type": "array"
+    },
+    "unverified_count": {
+      "type": "integer"
+    },
+    "verified_count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "domains"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description earns credit for adding beyond them: 'Cannot spend money' clarifies cost safety, and the scan_age_ms note warns that a stale verdict must not be read as fresh — a genuinely useful operational caveat not present in structured fields.

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?

Front-loads the trigger condition and the inventory contents, which is the right order. Slightly redundant tail ('Use before suggesting the user buy anything' overlaps with the opening 'what do I own' framing, and the cost note repeats the read-only idea), but nothing is wasted enough to hurt.

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?

A zero-param read tool with an output schema and full annotation coverage needs only trigger guidance, scope, and any behavioral caveat — all present, including the freshness warning about scan_age_ms. Nothing an agent needs to call it correctly is missing.

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?

Zero parameters, so there is nothing to document and the baseline is 4. The description does not attempt to invent or misdescribe inputs, which is correct behavior here.

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?

Names a precise verb and resource ('List the user's domain inventory') and immediately scopes the content: every domain with a verification challenge issued or completed, plus cached liveness, classification, title and expiry. An agent can distinguish it from siblings like audit_domain or verify_ownership without opening schemas.

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 states when to invoke ('at the start of any portfolio, renewal or what do I own question') and an exclusion-style rule ('before assuming which names the user holds', 'before suggesting the user buy anything'). This routes the agent ahead of quote_domain/suggest_names rather than leaving ordering to inference.

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

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