Skip to main content
Glama
gherisalim

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

introspection-graphql-master

Read-only

Explore the Sitecore GraphQL 'master' schema to inspect root operations, named types, search keywords, or full SDL for query building.

Instructions

Explores the Sitecore GraphQL 'master' schema. With no arguments it returns the root operations plus the Item interface — the whole contract for querying this endpoint, a couple of KB. Use type: "" for one type in full, search: "" to find one, and full: true only when you genuinely need every definition: a delivery schema's full SDL measured 777,501 characters (~194,000 tokens) on a live CM, two thirds of it repeated descriptions. Prefer the typed item/presentation tools when one already answers the question, and authoring-get-item-template or common-get-item-field to read a template's fields — both are far cheaper than the generated per-template types here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoWhen true, return the entire schema SDL. Very large — see the tool description for the measured size — so prefer 'type' or 'search'. Combine with includeDescriptions:false to cut it substantially.
typeNoReturn the full definition of one named type, or of one root operation (e.g. 'ArticlePage', 'createUser'). For an operation, the input and enum types its arguments reference are included too, so the result is enough to write the document. This is the argument to reach for once the index has told you the name.
searchNoFind types and operations whose name or description matches this keyword (e.g. 'media', 'workflow', 'publish'). Returns names and one-line summaries, not full definitions.
includeDescriptionsNoWhen false, strip all docstrings from the output. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

A4.9/5.0
Behavior5/5

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

Annotations supply only readOnlyHint=true; the description goes well beyond them by quantifying output size (777,501 characters, ~194,000 tokens, two thirds repeated descriptions) and revealing the cheaper paths, which materially changes how an agent budgets context. It also notes the default behavior with no arguments.

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?

Front-loads the default no-argument behavior, then escalates argument by argument, then closes with alternatives. Dense but every sentence carries a distinct decision-relevant fact; nothing is padding.

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

Completeness5/5

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

There is no output schema, so the description must describe returns itself, and it does: root operations plus Item interface at 'a couple of KB', names-and-summaries for search, full SDL with measured size. Nothing needed to call this introspection tool correctly is missing.

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% and the schema descriptions are already rich, so the baseline is 3; the description adds qualifying guidance such as reaching for 'type' only once the index has supplied a name and hinting at the full/includeDescriptions combination. The remaining parameter semantics (e.g. what 'search' returns) restate the schema rather than extend it.

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 ('Explores the Sitecore GraphQL master schema') and immediately defines the no-argument contract: root operations plus the Item interface. An agent can distinguish it from introspection-graphql-edge and query-graphql-master from the description alone.

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

Usage Guidelines5/5

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

Gives explicit routing rules per argument ('type' for one type in full, 'search' to find one, 'full' only when you genuinely need every definition), names alternatives (typed item/presentation tools, authoring-get-item-template, common-get-item-field), and states a when-NOT-to-use condition for full SDL.

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