Skip to main content
Glama

Get website

get_website
Read-only

Get the guide's public website settings: branding, hero image, description, location, contact phones, and the available themes and layouts.

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

Input Schema

NameRequiredDescriptionDefault
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

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 readOnlyHint=true, destructiveHint=false, and closed-world scope, so the safety profile is covered. The description adds that only 'public' settings are returned, which is useful scope context, but says nothing about behavior when no website exists yet or how large the themes/layouts list may be. No output schema exists, so return-value expectations rest mostly on the enumerated field list.

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?

One sentence, front-loaded with the verb and resource, followed by a field enumeration that earns its place by substituting for the missing output schema. No filler or restated title.

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 simple read-only tool with one optional parameter and no output schema, this is nearly complete: the returned fields are enumerated so the agent knows what to expect. The remaining gap is edge-case behavior (unconfigured website, error responses) and the absence of routing to update_website.

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 100% and the single business_id parameter is fully documented in-schema, including its source (list_businesses) and its optionality for single-business connections. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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?

Specific verb ('Get') plus resource ('guide's public website settings') and an explicit enumeration of what is included: branding, hero image, description, location, contact phones, themes and layouts. An agent can distinguish this read from update_website or import_website by the verb alone, though the description never names those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'Get' signals a read of site configuration, and the mention of 'available themes and layouts' hints at pre-update inspection. There is no explicit when-to-use, no statement that changes go through update_website, and no mention of when import_website would be the right call instead.

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.

Resources