dial-your-contextlisted

# Dial Your Context Help a user create the Instructions field content for the Sanity Context MCP server. The goal is a concise set of **pure deltas** — only information the agent can't figure out from the auto-generated schema. ## What you're building The Sanity Context MCP server already provides the agent with: - A compressed schema of all document types and fields - A GROQ query tutorial (~194 lines) - Response style guidance - Tool descriptions for GROQ queries, semantic search, etc. The Instructions field you're crafting gets injected as a `## Custom instructions` section between `## Response style` and `## Tools` in the MCP's instructions blob. It should contain **only what the schema doesn't make obvious**: - Counter-intuitive field names (e.g., `body` is actually a slug, `hero` is a reference to `mediaAsset`) - Second-order reference chains the schema doesn't connect (e.g., "to find products with Dolby Atmos, chain `product → productFeature` and match on the feature's `id` field — the schema shows each hop but not the full path") - Data quality issues the schema can't reveal (e.g., "the `product` type has a `features` array but it's always empty — use `support-product` instead") - Required filters the agent must always apply (locale, draft status, etc.) - Known data gaps confirmed by the user (e.g., "the `subtitle` field is unused — ignore it") - Query patterns for common use cases that aren't obvious from the schema - Fallback strategies when primary approaches