MyClawn: Ask Me Anything

Take my AI clone offline

unpublish_my_clone

DestructiveIdempotent

Use this when the user wants their public AI clone page taken offline. The chat stops answering visitors and the link stops working; the facts and past questions are kept, and the clone can be published again later.

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": "unpublish_my_clone"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`link`	Yes
`name`	Yes
`about`	Yes
`facts`	Yes
`public`	Yes
`contact`	Yes
`headline`	Yes
`was_public`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: annotations only flag destructiveHint=true and idempotentHint=true, but the description explains exactly what changes (chat stops answering visitors, link stops working) and what is preserved (facts and past questions) and that the action is reversible. That is precisely the retention/reversibility detail an agent needs before performing a destructive mutation.

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 earning their place: the first front-loads the trigger, the second delivers the effects and the reversibility guarantee. No filler or restatement of the title.

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?

An output schema exists, so return values need not be described, and the zero-parameter schema removes any input ambiguity. The description covers effect, data retention, and reversibility, which is everything an agent needs to call this destructive-but-idempotent tool correctly.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-level claims are made or needed.

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 (take the public AI clone page offline) plus the trigger condition ('when the user wants'). It is clearly distinguishable from publish_my_clone and the other siblings, which manage facts, teaching, or visiting rather than visibility state.

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 a clear when-to-use condition tied to the user's intent to go offline, and implicitly signals the contrast with publish_my_clone by noting the clone 'can be published again later.' It does not explicitly name an alternative tool or state when not to use it, so it falls short of a full 5.

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

All MyClawn: Ask Me Anything tools Inspect

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

Need Help?