@malloy-publisher/create-malloy-package 0.0.11 → 0.0.12

package/README.md

@@ -77,7 +77,7 @@ this workspace. That briefing is `AGENTS.md`, or `AGENTS.malloy.md` in a directo
 that already had an `AGENTS.md` of its own; see "Running it again" below.
 
 A directory nobody has trusted yet is a second gate, separate from connecting the MCP
-server: Claude Code lists the `malloy_*` tools and then refuses every call, and a
+server: Claude Code lists the Malloy tools and then refuses every call, and a
 `.claude/settings.json` allowlist is discarded rather than merged. Start Claude Code
 interactively in the directory once and answer the trust prompt, which is asked once per
 directory. A headless run is never asked, so it cannot clear the gate either. You will

package/dist/index.js

@@ -674,7 +674,7 @@ var MCP_PORT = 4040;
 var ALT_PUBLISHER_PORT = PUBLISHER_PORT + 100;
 var ALT_MCP_PORT = MCP_PORT + 100;
 var BIND_HOST = "127.0.0.1";
-var SERVER_VERSION = "0.2.3";
+var SERVER_VERSION = "0.2.4";
 function startCommandFor(envName) {
   return `npx -y @malloy-publisher/server@${SERVER_VERSION} --server_root . ` + `--config ./publisher.config.json --host ${BIND_HOST} ` + `--watch-env ${envName}`;
 }
@@ -1361,12 +1361,12 @@ function renderAgentsFile(result, host, envPackages) {
   const trustNote = host === "cursor" ? "" : [
     "",
     "One gate can void the reconnect fix below, and you cannot clear it yourself: if the",
-    "`malloy_*` tools are listed but every call is refused, the usual cause is that this",
+    "Malloy tools are listed but every call is refused, the usual cause is that this",
     "workspace has not been trusted, which also discards a `.claude/settings.json` allowlist.",
     "A human has to start Claude Code interactively in this directory once and answer the",
     "trust prompt; a non-interactive run is never asked, so it cannot clear the gate either.",
     "Tell the user and leave the choice to them. You will know the prompt was answered when a",
-    "`malloy_*` call returns data instead of being refused. If that does not change it, the",
+    "Malloy tool call returns data instead of being refused. If that does not change it, the",
     "other cause is a `malloy` server whose own approval was never given, which the user",
     "clears in the same `/mcp` panel named below. If the tools are not listed at all, this",
     "gate is not the cause, so read on.",
@@ -1420,7 +1420,7 @@ function otherPackagesParagraph(result, others, restBase) {
   const opening = result.packageCreated ? `This file is regenerated on every run and details only the package that run created. \`publisher.config.json\` registers ${others.length} other package${plural} in the \`${result.envName}\` environment` : `This run created no package. \`publisher.config.json\` registers ${others.length} package${plural} in the \`${result.envName}\` environment`;
   const named = others.every(isNameableHere) ? `: ${others.map((name) => `\`${name}\``).join(", ")}` : `, whose names this file does not repeat because at least one of them is outside the character set Publisher accepts in a URL`;
   const shape = result.packageCreated ? `the one above with the package name changed` : `\`${restBase("<package>")}\``;
-  return `${opening}${named}. Nothing here has read those models, so use ` + `\`malloy_getContext\`, or read the \`.malloy\` file in each package's ` + `own directory, for its source, field, and view names. Their REST bases ` + `are ${shape}. The packages endpoint further down lists what the running ` + `server actually mounted, which is the only answer that counts.`;
+  return `${opening}${named}. Nothing here has read those models, so use ` + `\`get_context\`, or read the \`.malloy\` file in each package's ` + `own directory, for its source, field, and view names. Their REST bases ` + `are ${shape}. The packages endpoint further down lists what the running ` + `server actually mounted, which is the only answer that counts.`;
 }
 function isNameableHere(name) {
   try {

package/package.json

@@ -1,7 +1,7 @@
 {
    "name": "@malloy-publisher/create-malloy-package",
    "description": "Scaffold a Malloy Publisher package and a local agent workspace, so one command takes you from nothing to an agent that can query your data.",
-   "version": "0.0.11",
+   "version": "0.0.12",
    "license": "MIT",
    "type": "module",
    "engines": {
@@ -45,7 +45,7 @@
       "test:e2e": "bun test --timeout 180000 tests/e2e"
    },
    "dependencies": {
-      "@malloy-publisher/skills": "^0.1.13",
+      "@malloy-publisher/skills": "^0.1.16",
       "commander": "^12.1.0"
    },
    "devDependencies": {

package/templates/AGENTS.md

@@ -46,8 +46,8 @@ returning the old model's rows; it may instead make the source vanish, so every
 fails with `Reference to undefined object '<source>'`. Either way the failure goes only
 to the server's stdout, which you are not reading if you started it in the background.
 So a query that succeeds after an edit is not proof the edit compiled, and the rows you
-get back may be the old model's. Compile-check the edit with `malloy_compile`, or reload with
-`malloy_reloadPackage` afterwards (both described below, and reload has a REST form for a
+get back may be the old model's. Compile-check the edit with `compile_model`, or reload with
+`reload_package` afterwards (both described below, and reload has a REST form for a
 script or an unattended run); either one reports the failure that watch mode swallowed.
 
 Poll until it reports serving rather than assuming a fixed wait; the first run
@@ -141,14 +141,16 @@ from the database it replaces.
 
 Two interfaces reach the same models with the same governance.
 
-MCP, for an interactive agent: the tools are `malloy_getContext` (discover
-environments, packages, sources, and fields), `malloy_executeQuery` (run a view or
-ad-hoc Malloy and get JSON back), `malloy_compile` (compile-check a snippet of Malloy
+MCP, for an interactive agent: the tools are `list_packages` (name the
+environments and the packages in each, which is where `get_context`'s required
+scope comes from), `get_context` (discover the sources, views, and fields inside
+one of those packages), `execute_query` (run a view or
+ad-hoc Malloy and get JSON back), `compile_model` (compile-check a snippet of Malloy
 against the model, so it takes the snippet as a required `source` argument; it reports
 the model file's own errors too),
-`malloy_reloadPackage` (pick up on-disk model edits with no restart, and surface a
+`reload_package` (pick up on-disk model edits with no restart, and surface a
 watch-mode recompile that failed), and
-`malloy_searchDocs`, and `malloy_searchDatabaseSchema` (find the tables in a database
+`search_malloy_docs`, and `search_database_schema` (find the tables in a database
 connection by plain-English description, for modelling data that is not in this package
 yet; it returns each table's columns and the `source:` line to start from). {{mcpNote}}
 
@@ -167,10 +169,10 @@ curl -s http://localhost:{{port}}/api/v0/environments/{{envName}}/packages
 That list is what this workspace serves. This file is not: it describes at most one
 package, the one the scaffolder created on the run that wrote this file. A workspace
 scaffolded more than once serves more than that, so take the packages, sources and
-views you do not see here from the list above and from `malloy_getContext`, never
+views you do not see here from the list above and from `get_context`, never
 from their absence here.
 {{trustNote}}
-If you started this server yourself in this session, your `malloy_*` tools will not
+If you started this server yourself in this session, your Malloy tools will not
 appear however long you wait: an MCP client fixes its tool list when it connects, so
 it never saw a server that did not yet exist. You cannot reconnect yourself. Say so,
 and {{reconnectNote}} Do not quietly switch to curl instead and call it done: it

package/templates/model.custom.malloy

@@ -6,8 +6,8 @@
 // This model was scaffolded from a data file whose columns are not known ahead of
 // time, so it starts with just a row count. Build it out for your columns: group_by
 // a column to break the count down, and define measures like
-// `total_amount is amount.sum()`. Validate edits with malloy_compile and run new
-// views by name with malloy_reloadPackage. The malloy-modeling skill walks through
+// `total_amount is amount.sum()`. Validate edits with compile_model and run new
+// views by name with reload_package. The malloy-modeling skill walks through
 // turning a raw table into a semantic model.
 
 source: {{sourceName}} is duckdb.table('{{dataPath}}') extend {

package/templates/model.custom.xlsx.malloy

@@ -137,8 +137,8 @@
 // Beyond that this is the same starting point as any seeded package: the
 // scaffolder does not read your columns, so it begins with a row count. Build it
 // out for your columns: group_by a column to break the count down, and define
-// measures over the numeric ones. Validate edits with malloy_compile and run new
-// views by name with malloy_reloadPackage. The malloy-modeling skill walks
+// measures over the numeric ones. Validate edits with compile_model and run new
+// views by name with reload_package. The malloy-modeling skill walks
 // through turning a raw table into a semantic model.
 
 source: {{sourceName}} is duckdb.table('{{dataPath}}') extend {

package/templates/model.default.malloy

@@ -7,8 +7,8 @@
 // no credentials and no build step. DuckDB auto-detects the header row and column
 // types. Edit this file and the dev server recompiles it, because it boots in
 // watch mode; AGENTS.md carries the command that starts it for this workspace.
-// An agent can validate a change with malloy_compile and run new views by name
-// with malloy_reloadPackage.
+// An agent can validate a change with compile_model and run new views by name
+// with reload_package.
 
 source: {{sourceName}} is duckdb.table('data/sales.csv') extend {
   primary_key: id