Skip to main content
Glama
Sign In

OneLence

by com.onelence
OverviewDiscussionsAdmin

Register a site

onelence_register_site

Adds a website to this workspace so it can send tracking data. Owners and admins only; limited by the plan's site capacity. The preview needs domain. Two steps: call with the change to get a summary and a confirmation_id, show the summary to the user, and only after they agree call again with just confirmation_id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "onelence_register_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoDomain such as example.com.
confirmation_idNoOnly when applying: the confirmation_id from the preview, after the user agreed.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "oneOf": [
+    {
+      "properties": {
+        "confirmation_id": {
+          "type": "string"
+        },
+        "expires_at": {
+          "type": "string"
+        },
+        "next_step": {
+          "type": "string"
+        },
+        "object": {
+          "const": "write_preview",
+          "type": "string"
+        },
+        "status": {
+          "const": "confirmation_required",
+          "type": "string"
+        },
+        "summary": {
+          "properties": {
+            "details": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "title",
+            "details"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "object",
+        "status",
+        "confirmation_id",
+        "expires_at",
+        "summary",
+        "next_step"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "object": {
+          "const": "write_result",
+          "type": "string"
+        },
+        "result": {
+          "anyOf": [
+            {
+              "properties": {
+                "default": {
+                  "type": "boolean"
+                },
+                "domain": {
+                  "type": "string"
+                },
+                "id": {
+                  "type": "string"
+                },
+                "object": {
+                  "const": "site",
+                  "type": "string"
+                },
+                "status": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                }
+              },
+              "required": [
+                "object",
+                "id",
+                "domain",
+                "status",
+                "default"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "status": {
+          "const": "applied",
+          "type": "string"
+        }
+      },
+      "required": [
+        "object",
+        "status",
+        "result"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the two-step preview/confirmation protocol, that the first call returns a summary plus confirmation_id, that the user must agree before applying, and the second call takes only confirmation_id. It also surfaces authorization scope and a plan-capacity limit, which the annotations (readOnlyHint=false, destructiveHint=false, non-idempotent) do not convey.

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-loaded with purpose, then constraints, then the two-step flow. Compact and mostly waste-free, though 'The preview needs domain' and 'call with the change' are slightly clipped phrasings that could be tighter.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with an output schema, the description covers authorization, capacity limits, and the confirmation workflow an agent must follow. The only gap is failure handling, such as what happens when the domain is already registered or the plan limit is hit.

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, but the description adds real meaning: domain is needed for the preview call, and the apply call passes confirmation_id alone. This clarifies the conditional shape of the two parameters beyond the field-level text.

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 ('Adds a website to this workspace so it can send tracking data'), including the downstream effect of the action. No sibling in the tool list registers sites, so it is unambiguously distinguishable from the get_/list_/update_ family.

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?

Gives clear preconditions: 'Owners and admins only' and 'limited by the plan's site capacity'. No explicit when-not-to-use or alternative tool is named, but there is no competing sibling for this operation, so the guidance is effectively complete.

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

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