Skip to main content
Glama

Get Site

get_site
Read-onlyIdempotent

Get the full details of a website, including business info, design tokens, pages, and all block content. Use this to understand what's currently on the site before making edits.

Annotations: read-only=true, destructive=false, idempotent=true, open-world=false. Why: Reads data only and changes nothing (read-only, so trivially idempotent). Closed-world: it touches only Zarla's own database.

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": {
      "site_id": "<site_id>"
    },
    "name": "get_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site ID (from create_site or list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, idempotent, and closed-world, so the safety profile is fully covered. The description adds that the response is comprehensive ('full details' spanning several sub-resources), which hints at payload size, but says nothing about cost, pagination, or what happens when the site has no content.

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?

Two tight sentences with the payload list first and the usage trigger second; nothing is buried. The appended annotation rationale restates structured metadata and adds length without adding decision value.

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 carries the burden of telling the agent what comes back, and it does so at a useful level of granularity (business info, design tokens, pages, blocks). Given a one-parameter read tool with full annotations, little else is needed.

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?

There is a single required parameter whose schema coverage is 100%, including UUID format and a pointer to create_site/list_sites for obtaining it. The description adds no parameter-level meaning beyond that, which is the expected baseline.

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?

States a specific verb and resource (get the full details of a website) and enumerates the payload: business info, design tokens, pages, block content. That enumeration implicitly separates it from get_page, which covers a single page, though no sibling is named.

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 trigger: use it to understand what's currently on the site before making edits. There is no explicit when-not or named alternative (e.g. get_page for a single page), so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.