Skip to main content
Glama
marlondivino

OpenCode MCP Server

by marlondivino

refine_prompt

Refines prompts by applying semantic memory to improve context and efficiency, reducing token usage.

Instructions

Refines a prompt using semantic memory to make it more contextual and efficient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesThe original prompt that needs refinement.

Implementation Reference

  • The CallTool handler for 'refine_prompt'. It takes the prompt argument, optionally retrieves relevant semantic memories via LanceDB vector search, and returns a refined prompt with context.
    if (name === "refine_prompt") {
      const prompt = args?.prompt as string;
      let contextExtra = "";
    
      // Try to fetch relevant memories
      if (table) {
        const queryVector = await getEmbedding(prompt);
        const results = await table.vectorSearch(queryVector).limit(3).toArray();
        
        if (results.length > 0) {
          contextExtra = "\n[Context Retrieved from Memory]:\n" + 
            results.map((r: any) => `- ${r.text}`).join("\n");
        }
      }
    
      return {
        content: [
          {
            type: "text",
            text: `[Refined Prompt]: ${prompt}\n${contextExtra}\n\n(Antigravity can now use the information above to generate a more precise response)`,
          },
        ],
      };
    }
  • Registration of 'refine_prompt' in the ListTools handler, including its description and inputSchema (requires a 'prompt' string).
      name: "refine_prompt",
      description: "Refines a prompt using semantic memory to make it more contextual and efficient.",
      inputSchema: {
        type: "object",
        properties: {
          prompt: {
            type: "string",
            description: "The original prompt that needs refinement.",
          },
        },
        required: ["prompt"],
      },
    },
  • src/index.ts:111-164 (registration)
    The CallToolRequestSchema handler that dispatches to 'refine_prompt' (alongside 'learn_context') based on the tool name.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      if (name === "learn_context") {
        const info = args?.information as string;
        const category = (args?.category as string) || "general";
        
        const vector = await getEmbedding(info);
        
        const data = [{
          vector,
          text: info,
          category,
          timestamp: new Date().toISOString()
        }];
    
        if (!table) {
          table = await db.createTable(TABLE_NAME, data);
        } else {
          await table.add(data);
        }
    
        return {
          content: [{ type: "text", text: `Learned and stored in semantic memory: "${info}"` }],
        };
      }
    
      if (name === "refine_prompt") {
        const prompt = args?.prompt as string;
        let contextExtra = "";
    
        // Try to fetch relevant memories
        if (table) {
          const queryVector = await getEmbedding(prompt);
          const results = await table.vectorSearch(queryVector).limit(3).toArray();
          
          if (results.length > 0) {
            contextExtra = "\n[Context Retrieved from Memory]:\n" + 
              results.map((r: any) => `- ${r.text}`).join("\n");
          }
        }
    
        return {
          content: [
            {
              type: "text",
              text: `[Refined Prompt]: ${prompt}\n${contextExtra}\n\n(Antigravity can now use the information above to generate a more precise response)`,
            },
          ],
        };
      }
    
      throw new Error(`Tool not found: ${name}`);
    });
  • src/index.ts:72-107 (registration)
    The ListToolsRequestSchema handler that registers 'refine_prompt' as an available tool with its input schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "refine_prompt",
            description: "Refines a prompt using semantic memory to make it more contextual and efficient.",
            inputSchema: {
              type: "object",
              properties: {
                prompt: {
                  type: "string",
                  description: "The original prompt that needs refinement.",
                },
              },
              required: ["prompt"],
            },
          },
          {
            name: "learn_context",
            description: "Memorizes important information (preference, technical rule, context) for future use.",
            inputSchema: {
              type: "object",
              properties: {
                information: {
                  type: "string",
                  description: "The information to be remembered.",
                },
                category: {
                  type: "string",
                  description: "Information category (e.g., 'preference', 'architecture', 'style').",
                },
              },
              required: ["information"],
            },
          },
        ],
  • getEmbedding is a helper function that uses Ollama to generate embeddings for text, used by refine_prompt to perform vector similarity search.
    async function getEmbedding(text: string): Promise<number[]> {
      const response = await ollama.embed({
        model: EMBEDDING_MODEL,
        input: text,
      });
      return response.embeddings[0]!;
    }
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'using semantic memory' but does not explain side effects (e.g., memory updates), performance implications, or whether the operation is read-only or modifying. This leaves the agent uncertain about expectations.

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?

The description is a single, efficient sentence that starts with the verb. No unnecessary words or structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and simple input, the description should explain what 'refinement' means and how semantic memory is used. It does not specify the output format or any side effects, leaving the agent without enough context to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter, so baseline is 3. The description does not add any meaning beyond the schema's description of 'The original prompt that needs refinement.' No additional constraints, formats, or examples are given.

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?

The description clearly states the verb 'refines' and the resource 'prompt', and uses 'semantic memory' to add specificity. It distinguishes from sibling 'learn_context' by focusing on prompt refinement rather than context learning.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus 'learn_context' or other alternatives. The description implies it is for making prompts more contextual and efficient, but does not specify prerequisites, exclusions, or when refinement is appropriate.

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/marlondivino/open-code-as-mcp'

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