Velixar MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

velixar_refine_context

Refine an existing context package by expanding a section, filling a gap, or adding a topic. Supports single or batch actions for targeted improvements.

Instructions

Expand a section, fill a gap, or add a topic to an existing context package. Accepts a single action or an array of actions for batch refinement.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context_id": "<context_id>"
    },
    "name": "velixar_refine_context"
  }
}

Input Schema

Name	Required	Description
`action`	No	What to do (single action)
`target`	No	Section label, gap name, or new topic (single action)
`actions`	No	Batch: array of {action, target, budget?} for multiple refinements in one call
`context_id`	Yes	ID from prepare_context response
`additional_budget`	No	Extra tokens (default 1000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 30, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions batch refinement but does not disclose side effects (e.g., whether the original context is modified or replaced), reversibility, or limits. The return format is also omitted as there is no output schema.

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 two sentences, front-loaded with the core purpose. Every sentence is essential, with no wasted words or redundancy.

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 the absence of an output schema and the complexity of refinement (e.g., interaction between action/target and actions/budget), the description lacks details on return values, state changes, and parameter interplay. It is incomplete for a tool with 5 parameters.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema; it merely reiterates that single or batch actions are accepted. No additional parameter constraints or clarifications are provided.

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 tool's purpose: expanding sections, filling gaps, or adding topics to an existing context package. It uses specific verbs and resources, and distinguishes from sibling tools like velixar_context (creation) and velixar_prepare_context (preparation).

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. The required context_id parameter implies prior context preparation, but this is not stated explicitly.

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