Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

common-get-cache

Read-only

Retrieve Sitecore cache sizes and occupancy. Pass a cache name with wildcards or omit to list all caches.

Instructions

Gets information about Sitecore caches, with their size and occupancy. Omit name to return every cache. Cache names contain square brackets ('master[items]'); pass one exactly as reported and it is matched literally, or use * / ? for a wildcard.

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-cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn the unprojected .NET object graph. Very large (100,000+ chars/item); diagnostics only.
nameNoThe name of the cache to retrieve, e.g. 'master[items]'. Use * or ? for wildcard matching. If not provided, all caches will be returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

A4.4/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description earns credit for adding real behavior: exact literal matching versus wildcard matching, and the square-bracket gotcha in cache names that would otherwise cause silent mismatches. It never states auth or rate-limit behavior, so it is not a 5.

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?

Three sentences, all load-bearing: purpose and return fields first, then the default behavior, then the matching rules. Zero filler, front-loaded, no repetition of the schema.

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 2-param, no-required, read-only tool with no output schema, the description covers what is returned (size and occupancy), the default scope, and the tricky matching semantics. It leaves the 'full' projection caveat entirely to the schema, which is acceptable but a minor gap given the schema already flags it as diagnostics-only.

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 100% (baseline 3), and the description adds meaning beyond the schema by warning that names contain square brackets and are matched literally when passed verbatim, versus '*'/'?' for patterns. This disambiguates the most error-prone parameter for the agent.

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?

States a specific verb and resource ('Gets information about Sitecore caches') plus what the payload contains ('size and occupancy'). No sibling tool targets caches, so there is no ambiguity to resolve against the ~90 item/security siblings.

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?

'Omit name to return every cache' gives a clear conditional for the default/no-arg case, and the wildcard guidance tells the agent how to widen a query. It stops short of explicit when-not/alternative routing, but no real alternative exists among siblings.

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