Skip to main content
Glama
Sign In

Cactal

by ai.cactal
OverviewDiscussionsAdmin

Get a website

websites_get
Read-onlyIdempotent

Returns a single website by websiteId, or by its organizationSlug + websiteSlug pair when starting from a URL — provide exactly one of the two identifications. The response includes whether the caller can manage the website’s CMS schema and domains. Websites in the trash remain retrievable by id (see websites.list with status=deleted for their purge timing); slug lookups only resolve active websites, and inaccessible or deleted resources return 404.

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

Input Schema

NameRequiredDescriptionDefault
websiteIdNoWebsite id. Provide either this or the `organizationSlug` + `websiteSlug` pair.
websiteSlugNoWebsite URL slug within the organization. Pair with `organizationSlug`.
organizationSlugNoURL slug of the owning organization. Pair with `websiteSlug` to look the website up by slug instead of id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that the response includes management permissions for CMS schema and domains, that trash websites are retrievable by id but not by slug, and that inaccessible or deleted resources return 404. This adds meaningful behavioral and error-handling context not present in the annotations.

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?

The description is three dense sentences, front-loaded with the lookup modes and then the behavioral caveats. Each sentence carries useful information about identification, permissions, or lookup behavior, with no filler.

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?

With no output schema, the description covers the key response permission detail and important 404/trash/slug caveats, which is sufficient for correct invocation. It does not enumerate the returned website object’s fields, but that is a minor omission for a simple get tool.

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 already 100%, so the schema documents each parameter individually. The description still adds the higher-level exclusivity rule (“exactly one of the two identifications”) and clarifies behavior differences between id and slug lookup, which improves parameter semantics beyond the per-field descriptions.

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?

The description uses the specific verb “Returns” with the precise resource “a single website” and explicitly distinguishes the two lookup modes: by websiteId or by organizationSlug + websiteSlug. This is enough for an agent to identify it against sibling list/create/update tools without opening the schema.

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?

It states the mutually exclusive identification conditions (“provide exactly one of the two identifications”), explains that slug lookups only resolve active websites, and notes that deleted websites remain retrievable by id while pointing to websites.list for purge timing. These are concrete when-to-use and when-not-to-use rules with a relevant alternative.

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

All Cactal toolsInspect
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