Skip to main content
Glama

export_domain_pack

Export a project's domain knowledge—abbreviations, conventions, terms, and associations—as a portable YAML pack for review, curation, and reuse in other projects or tools.

Instructions

Export the project's full domain knowledge as a portable YAML pack — abbreviations, conventions, domain terms, and concept associations. Use when asked to 'export conventions', 'create a domain pack', or 'share naming rules'. The output can be reviewed, curated, and saved for use in other projects or tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition/schema for 'export_domain_pack' — defines the MCP name, description, prompt snippet, and empty parameters object (no input args).
    {
      mcpName: "export_domain_pack",
      label: "Export Domain Pack",
      description:
        "Export the project's full domain knowledge as portable YAML — " +
        "abbreviations, conventions, domain terms, concept associations.",
      promptSnippet:
        "ontomics_export_domain_pack: export domain knowledge as YAML",
      parameters: Type.Object({}),
    },
  • All tools including 'export_domain_pack' are registered via pi.registerTool() in a loop over toolDefs(). The registered name becomes 'ontomics_export_domain_pack'.
    for (const def of toolDefs()) {
      pi.registerTool({
        name: `ontomics_${def.mcpName}`,
        label: def.label,
        description: def.description,
        promptSnippet: def.promptSnippet,
        promptGuidelines: [
          "Use ontomics tools BEFORE grep/glob for semantic codebase questions.",
        ],
        parameters: def.parameters,
        async execute(_toolCallId, params, _signal, onUpdate, _ctx) {
          onUpdate?.({
            content: [{ type: "text", text: `Querying ontomics: ${def.mcpName}...` }],
          });
          try {
            const mcp = await getClient();
            const text = await mcp.callTool(def.mcpName, cleanArgs(params));
            return { content: [{ type: "text", text }] };
          } catch (err) {
            throw new Error(
              `ontomics ${def.mcpName} failed: ${err instanceof Error ? err.message : String(err)}`,
            );
          }
        },
      });
    }
  • Handler function: delegates to the external 'ontomics' binary via MCP client's callTool("export_domain_pack", {}), sending the tool name and cleaned parameters over JSON-RPC stdio to the external process.
    async execute(_toolCallId, params, _signal, onUpdate, _ctx) {
      onUpdate?.({
        content: [{ type: "text", text: `Querying ontomics: ${def.mcpName}...` }],
      });
      try {
        const mcp = await getClient();
        const text = await mcp.callTool(def.mcpName, cleanArgs(params));
        return { content: [{ type: "text", text }] };
      } catch (err) {
        throw new Error(
          `ontomics ${def.mcpName} failed: ${err instanceof Error ? err.message : String(err)}`,
        );
      }
  • McpClient helper class that communicates with the external 'ontomics' binary over stdio JSON-RPC. The callTool method sends a tools/call request, dispatching to the actual server-side implementation of 'export_domain_pack'.
    class McpClient {
      private proc: ChildProcess;
      private rl: ReadlineInterface;
      private nextId = 1;
      private pending = new Map<
        number,
        { resolve: (v: unknown) => void; reject: (e: Error) => void }
      >();
    
      private constructor(proc: ChildProcess) {
        this.proc = proc;
        this.rl = createInterface({ input: proc.stdout! });
        this.rl.on("line", (line: string) => this.onLine(line));
        proc.stderr?.on("data", () => {});
      }
    
      static async start(binaryPath: string, cwd: string): Promise<McpClient> {
        const proc = spawn(binaryPath, ["serve"], {
          cwd,
          stdio: ["pipe", "pipe", "pipe"],
        });
        const client = new McpClient(proc);
        await client.request("initialize", {
          protocolVersion: "2024-11-05",
          capabilities: {},
          clientInfo: { name: "pi-ontomics", version: "1.0.0" },
        });
        client.notify("notifications/initialized", {});
        return client;
      }
    
      async callTool(
        name: string,
        args: Record<string, unknown>,
      ): Promise<string> {
        const result = (await this.request("tools/call", {
          name,
          arguments: args,
        })) as { content?: Array<{ text?: string }> };
        const text = result.content?.[0]?.text ?? JSON.stringify(result);
        return text;
      }
    
      dispose(): void {
        this.proc.kill();
        this.rl.close();
      }
    
      get alive(): boolean {
        return !this.proc.killed && this.proc.exitCode === null;
      }
    
      private request(method: string, params: unknown): Promise<unknown> {
        const id = this.nextId++;
        return new Promise((resolve, reject) => {
          this.pending.set(id, { resolve, reject });
          this.write({ jsonrpc: "2.0", id, method, params });
        });
      }
    
      private notify(method: string, params: unknown): void {
        this.write({ jsonrpc: "2.0", method, params });
      }
    
      private write(msg: unknown): void {
        this.proc.stdin!.write(JSON.stringify(msg) + "\n");
      }
    
      private onLine(line: string): void {
        if (!line.trim()) return;
        try {
          const msg = JSON.parse(line) as {
            id?: number;
            result?: unknown;
            error?: { message: string };
          };
          if (msg.id != null && this.pending.has(msg.id)) {
            const { resolve, reject } = this.pending.get(msg.id)!;
            this.pending.delete(msg.id);
            if (msg.error) reject(new Error(msg.error.message));
            else resolve(msg.result);
          }
        } catch {
          // ignore non-JSON lines (e.g. stderr leaks)
        }
      }
    }
Behavior4/5

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

No annotations provided, but description effectively explains non-destructive export behavior and output nature. Does not mention potential size or scope limitations, but overall transparent given zero parameters.

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?

Three concise sentences: first defines action/content, second provides usage guidance, third describes output utility. No redundant or missing information.

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, but description sufficiently explains the YAML pack output and its contents. With zero parameters, the description covers all necessary context for an agent to use the tool correctly.

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?

Tool has no parameters, and schema coverage is 100% (empty). Description adds no further parameter info, which is acceptable as baseline for zero-parameter tools.

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?

Clearly states it exports full domain knowledge as a portable YAML pack, listing specific contents (abbreviations, conventions, terms, associations) and use cases. Distinguishes from sibling tools like list_concepts or list_conventions by being a comprehensive export.

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

Usage Guidelines4/5

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

Explicitly defines when to use with phrases like 'export conventions', 'create a domain pack', 'share naming rules'. Lacks direct comparison to alternative tools or when not to use, but trigger phrases are clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EtienneChollet/ontomics'

If you have feedback or need assistance with the MCP directory API, please join our Discord server