ATTIM

Claim site

claim_site

Keep a temporary site so it no longer expires. Signed in, it moves into the account now. Otherwise pass the user's email: ATTIM emails them a link that keeps it and creates their free account. Without an email, the user is asked to connect ATTIM here.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "claimToken": "<claimToken>"
    },
    "name": "claim_site"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes
`email`	No	The user's own email, when no account is connected.
`claimToken`	Yes
`workspaceId`	No

Output Schema

Name	Required	Description	Default
`slug`	Yes
`claimed`	No
`pending`	No
`siteUrl`	Yes
`linkExpiresAt`	No
`siteExpiresAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / claimToken / minLength
```
Removed value: -8
```
- changedInput schema / properties / email / description
```
Previous value: -"The user's own email address, when no ATTIM account is connected. ATTIM emails it a link that keeps the site."New value: +"The user's own email, when no account is connected."
```
- removedInput schema / properties / email / minLength
```
Removed value: -3
```
- removedInput schema / properties / slug / minLength
```
Removed value: -1
```
- removedInput schema / properties / workspaceId / minimum
```
Removed value: -1
```
- removedOutput schema / properties / anonymous
```
Removed value: -{
-  "type": "boolean"
-}
```
- removedOutput schema / properties / cooldownSeconds
```
Removed value: -{
-  "type": "integer"
-}
```
- removedOutput schema / properties / email
```
Removed value: -{
-  "type": "string"
-}
```
First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only say it is a non-read-only, non-destructive, non-idempotent, closed-world call. The description adds real behavior: the site is transferred into the caller's account, or an email link is sent that also provisions a free account, or the user is prompted to connect ATTIM. That is meaningful side-effect disclosure, though failure modes (expired or invalid claim token) are not covered.

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?

Three short sentences, front-loaded with the core purpose before the conditional branches. No filler. The word 'here' in the final sentence is slightly loose, but nothing is genuinely wasted.

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

Completeness3/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. However, for a mutation that can create an account and send an email, the definition leaves the required claimToken's origin and validation behavior, plus error/expiry handling, entirely unaddressed.

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?

Schema description coverage is only 25%, so the description must compensate. It explains the email parameter's role and what happens when it is omitted, which is useful. But the required claimToken is never explained, nor is workspaceId, leaving the most opaque required parameter undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and outcome: keep a temporary site so it no longer expires. That is distinct from siblings like publish_site, copy_site, or update_site. It does not explicitly name an alternative tool, so it stops short of a 5.

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 lays out three concrete invocation branches keyed on the user's auth state: signed in, signed out with an email, and signed out without one. That is clear contextual guidance. It does not address when-not-to-use or name a sibling alternative, so it is not a 5.

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

All ATTIM tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?