Velixar MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

velixar_identity

Create, read, update, and delete user identity fields such as expertise and communication style for workspace-scoped profile memory across AI sessions.

Instructions

User profile — preferences, expertise, communication style, recurring goals, stable constraints. Supports get (default), store, update, delete, list, and history actions. Workspace-scoped.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "velixar_identity"
  }
}

Input Schema

Name	Required	Description
`field`	No	Identity field to store/update/delete/history (e.g. "expertise", "communication_style")
`value`	No	Value to store/update (string or array of strings)
`action`	No	Action (default: get)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses the workspace-scoped nature and supported actions but does not describe behavioral traits such as permission requirements, what happens on deletion, or the effect of updates. For a mutation tool, this is insufficient.

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, and every word adds value. No redundancy or extraneous information.

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?

No output schema exists, so the description should explain return values or behavior (e.g., what get returns, what list returns). It does not. Additionally, it lacks details on error scenarios or idempotency. The tool has 3 optional params and an enum, but the description doesn't fully cover the operational context.

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%, baseline 3. The description lists example field values (preferences, goals, constraints) that go slightly beyond the schema's examples, adding minor value but not compensating significantly for the 0% coverage gap in the schema (which is already 100%).

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 this tool manages user profile fields (preferences, expertise, communication style, etc.) and lists all supported actions (get, store, update, delete, list, history). This distinguishes it from generic sibling tools like velixar_store or velixar_list by specifying the identity/profile scope.

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

Usage Guidelines3/5

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

The description implies the tool is for managing user profile fields but does not explicitly state when to use it over alternatives (e.g., velixar_context for context data, velixar_store for arbitrary data). No guidance on prerequisites or exclusions is provided.

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