Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

common-get-archive

Read-only

Retrieve Sitecore database archives by name and database to inspect, back up, or migrate content; optionally return full diagnostic object graphs.

Instructions

Gets Sitecore database archives.

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": "common-get-archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn the unprojected .NET object graph. Very large (100,000+ chars/item); diagnostics only.
nameNoThe name of the archive to retrieve.
databaseNoThe database for which the archives should be retrieved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

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, so the safety profile is covered, but the description adds nothing beyond that — no note on what an archive result contains, expected size, or whether a database/name is required despite zero required params.

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?

A single short sentence with no filler and the resource front-loaded. It is efficient, though its brevity edges toward under-specification rather than crisp conciseness.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with a fully documented schema this is thin: it omits the distinction from common-get-archive-item, doesn't say what is returned, and gives no guidance on the absence of required parameters. An agent could call it, but not confidently over its siblings.

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%; the schema itself fully documents full (diagnostics/unprojected graph), name, and database. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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?

"Gets Sitecore database archives" states a clear verb and resource, so the basic purpose is legible. However, it does not differentiate from the near-identical sibling common-get-archive-item, leaving the agent to infer the scope difference between an archive and an item within an archive.

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?

The description contains no when-to-use guidance, no prerequisites, and no routing to alternatives. With siblings like common-get-archive-item and common-restore-archive-item present, an agent gets no signal about which to pick.

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

Deploy Server

Other Tools