Skip to main content
Glama
Antonytm

mcp-sitecore-server

by Antonytm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

introspection-graphql-default

Read-only

Explore the Sitecore GraphQL default schema: get root operations or a named type, search definitions, or fetch full SDL. Use typed item tools when possible.

Instructions

Explores the Sitecore GraphQL 'default' 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.5

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, so the safety profile is settled; the description goes well beyond by disclosing output shapes, the measured size of full SDL (777,501 chars / ~194,000 tokens), and that two thirds is repeated descriptions. It stops short of stating auth requirements or rate limits, so it is strong but not exhaustive.

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?

Front-loaded with the default behavior and cheap path, with the cost warning placed after the useful routing. Dense and mostly earning its sentences, though the multi-clause size-statistics sentence approaches verbosity.

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?

No output schema exists, but the description fully characterizes returns (root operations + Item interface by default, one type in full, names plus one-line summaries for search) and quantifies the expensive path. Nothing an agent needs to invoke it 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 description coverage is 100%, so the baseline is 3; the description adds real routing value on top by advising which argument to reach for (type after the index reveals a name, search for discovery, full sparingly, includeDescriptions to shrink output). That is genuine semantics beyond the schema text.

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 — exploring the Sitecore GraphQL 'default' schema — and even enumerates the default return payload (root operations plus the Item interface). It is distinguishable from siblings like query-graphql-default and authoring-introspect-schema without opening any schema.

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?

Explicitly routes among its own modes (type for one definition, search to find a name, full only when truly needed) and names alternative tools — 'prefer the typed item/presentation tools' and authoring-get-item-template / common-get-item-field — for reading template fields. This is exactly the when/when-not/alternatives guidance the dimension asks for.

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