@@ -215,9 +295,9 @@ export function Mcp() {
tools.
- By connecting to this MCP server, your AI assistant gains the ability to search and
- retrieve information from the ECMA-376 specification—making it much easier to work with
- Office Open XML.
+ By connecting to this MCP server, your AI assistant gains both prose search across the
+ ECMA-376 specification and deterministic schema lookup over the parsed XSDs—making it
+ much easier to work with Office Open XML.
diff --git a/brand.md b/brand.md
index a37e6be..56dd73f 100644
--- a/brand.md
+++ b/brand.md
@@ -52,7 +52,7 @@ The commercial document vendors (Aspose, Syncfusion, TX Text Control, Nutrient)
**Structural differentiators**:
- **Live previews** — Every XML example renders in real-time via SuperDoc. No other OOXML reference shows you what the XML actually produces.
- **Implementation notes from production** — Not spec commentary. Notes from building a shipping document engine against real-world documents.
-- **AI-native search** — MCP server with semantic vector search across 18,000+ spec chunks. The spec is searchable by meaning, not just keywords.
+- **AI-native reference** — MCP server with two tool families: prose search across 18,000+ spec chunks (ask questions in natural language) and deterministic schema lookup over the parsed XSDs (legal children, attribute lists, enum values, namespaces — exact answers, no hallucination).
- **Real document corpus** — Backed by docx-corpus (1M+ real documents). Observations are tested against actual documents in the wild, not just spec examples.
- **Format-first, tool-agnostic** — Useful whether you're building on SuperDoc, Aspose, your own renderer, or just trying to understand a .docx file.
@@ -133,7 +133,7 @@ _Use on homepage hero, social bios, link previews._
**Slogans for different contexts**:
- Developer discovery: "5,000 pages of spec. The 200 that matter. The notes you actually need."
-- AI/MCP context: "Ask the spec anything. Get answers grounded in implementation experience."
+- AI/MCP context: "Ask the spec anything, or query the schema directly. Two tool families, one server."
- Community pitch: "Hard-won OOXML knowledge, shared freely."
- SuperDoc connection: "Built by SuperDoc — DOCX editing and tooling. Open to everyone."
- Credibility: "Every example is a working document."
diff --git a/scripts/ingest-pdf/README.md b/scripts/ingest-pdf/README.md
index 8e051c0..a14cb5e 100644
--- a/scripts/ingest-pdf/README.md
+++ b/scripts/ingest-pdf/README.md
@@ -1,7 +1,7 @@
# PDF ingest (ECMA-376 prose corpus)
-Builds the semantic-search corpus that powers `search_ecma_spec` /
-`get_section` / `list_parts`. Each ECMA-376 part PDF is extracted into
+Builds the prose-search corpus that powers `ooxml_search` /
+`ooxml_section` / `ooxml_parts`. Each ECMA-376 part PDF is extracted into
section-aware markdown, chunked at ~6 KB boundaries, embedded with the
configured provider, and uploaded into `spec_content`.
diff --git a/scripts/ingest-xsd/README.md b/scripts/ingest-xsd/README.md
index 78cdba2..a417f5a 100644
--- a/scripts/ingest-xsd/README.md
+++ b/scripts/ingest-xsd/README.md
@@ -1,6 +1,6 @@
# XSD ingest (ECMA-376 schema graph)
-Builds the structural-query corpus that powers `ooxml_lookup_element`,
+Builds the structural-query corpus that powers `ooxml_element`,
`ooxml_children`, `ooxml_attributes`, etc. The XSDs published by Ecma
International for ECMA-376 Transitional are parsed and persisted as a
profile-scoped relational graph.
diff --git a/scripts/ingest-xsd/ingest.ts b/scripts/ingest-xsd/ingest.ts
index d4bb8be..caa2859 100644
--- a/scripts/ingest-xsd/ingest.ts
+++ b/scripts/ingest-xsd/ingest.ts
@@ -257,7 +257,7 @@ export async function ingestSchemaSet(opts: IngestSchemaSetOptions): Promise
inside CT_Para.
- // Should have type_ref AND profile membership so ooxml_lookup_element finds it.
+ // Should have type_ref AND profile membership so ooxml_element finds it.
const [textSym] = await db.sql`
SELECT s.id, s.type_ref FROM xsd_symbols s
WHERE s.local_name = 'text' AND s.kind = 'element' AND s.vocabulary_id = 'wml-main'
diff --git a/tests/mcp-server/ooxml-queries.test.ts b/tests/mcp-server/ooxml-queries.test.ts
index 7d5c5f2..93c8678 100644
--- a/tests/mcp-server/ooxml-queries.test.ts
+++ b/tests/mcp-server/ooxml-queries.test.ts
@@ -285,7 +285,7 @@ test("local element symbols are scoped per-owner (no cross-CT collapse)", async
test("xsd-builtin symbols have profile membership (lookupSymbolByTypeRef can follow xsd:string)", async () => {
// Built-ins like xsd:string are auto-created during inheritance resolution and
- // must be linked to xsd_symbol_profiles, otherwise ooxml_lookup_type for
+ // must be linked to xsd_symbol_profiles, otherwise ooxml_type for
// 'xsd:string' and lookupSymbolByTypeRef for {...XMLSchema}string return null.
const t = await lookupSymbolByTypeRef(
db.sql,
diff --git a/tests/mcp-server/tools-list.test.ts b/tests/mcp-server/tools-list.test.ts
new file mode 100644
index 0000000..ae02a94
--- /dev/null
+++ b/tests/mcp-server/tools-list.test.ts
@@ -0,0 +1,54 @@
+/**
+ * Snapshot the public MCP surface so a future rename or accidental drop
+ * (between TOOLS, OOXML_TOOL_DEFS, and the docs) fails CI.
+ *
+ * No DB access; we exercise tools/list and the initialize handler. tools/call
+ * is covered by the per-tool tests in ooxml-queries.test.ts.
+ */
+
+import { expect, test } from "bun:test";
+import { handleMcpRequest } from "../../apps/mcp-server/src/mcp.ts";
+
+const EXPECTED_TOOL_NAMES = [
+ // Prose search (over the spec PDFs)
+ "ooxml_search",
+ "ooxml_section",
+ "ooxml_parts",
+ // Schema lookup (over the parsed XSDs)
+ "ooxml_element",
+ "ooxml_type",
+ "ooxml_children",
+ "ooxml_attributes",
+ "ooxml_enum",
+ "ooxml_namespace",
+] as const;
+
+interface JsonRpcResponse {
+ jsonrpc: string;
+ id: number | string | null;
+ result?: { tools?: Array<{ name: string }>; serverInfo?: { name: string } };
+ error?: { code: number; message: string };
+}
+
+async function rpc(method: string, params?: unknown): Promise
{
+ const req = new Request("https://example.invalid/mcp", {
+ method: "POST",
+ headers: { "Content-Type": "application/json" },
+ body: JSON.stringify({ jsonrpc: "2.0", id: 1, method, params }),
+ });
+ // Env is unused for tools/list and initialize.
+ const env = { DATABASE_URL: "", VOYAGE_API_KEY: "" } as never;
+ const res = await handleMcpRequest(req, env);
+ return (await res.json()) as JsonRpcResponse;
+}
+
+test("tools/list returns the full ooxml_* tool set in the documented order", async () => {
+ const r = await rpc("tools/list");
+ const names = r.result?.tools?.map((t) => t.name) ?? [];
+ expect(names).toEqual([...EXPECTED_TOOL_NAMES]);
+});
+
+test("initialize advertises serverInfo.name as 'ooxml'", async () => {
+ const r = await rpc("initialize");
+ expect(r.result?.serverInfo?.name).toBe("ooxml");
+});