Skip to main content
Glama

Get site

site_get
Read-only

One site in full.

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": {
      "id": "<id>",
      "org": "<org>"
    },
    "name": "site_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe site's short name (its name lowercased, other characters made hyphens, e.g. deal-flow), or its client id.
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavior of its own beyond the phrase "in full" — no note on what happens when the site is missing, whether the id may be a name or client id, or what the payload resembles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words with zero padding, but the brevity is under-specification rather than economy: it is not a grammatical sentence and carries no actionable content. What is present is front-loaded and wastes no space.

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?

The tool is simple (two required, fully documented parameters), annotations cover the safety profile, and no output schema exists, so the structured fields do most of the work. Still, "in full" is the only hint at the return shape for a tool whose whole value is the detail it returns, leaving a modest gap.

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 both parameters are documented in detail, including the slug/hyphen normalization rule and the enum for org, so the baseline of 3 applies. The description contributes nothing to parameter meaning that the schema does not already say.

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

Purpose3/5

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

"One site in full" identifies the resource (a site) and implies a single full-detail fetch rather than a listing, which faintly distinguishes it from sibling site_list. But it is a verbless fragment that never states the operation outright, so the agent must infer "get" from the name and title.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to reach for this after site_list to expand a result, nothing rules out site_update or site_attach for other needs, and no prerequisite (the org parameter being mandatory) is restated. The only usable routing signal is the singular-vs-plural sibling name, which the description does not exploit.

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