Vilix AI

search_semantic

Read-onlyIdempotent

Optional. Meaning-based search over the user's past messages.

Use when get_context isn't enough — e.g. the user asks about something specific from before. source (optional) restricts to one platform label as saved (e.g. "ChatGPT", "Claude", "Cursor"). limit optional (default 10, max 25).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`source`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`inbox`	No
`message`	No
`results`	No
`instruction`	No
`upgrade_url`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the burden is lower. The description adds useful behavioral context: the search covers past messages and source restricts to saved platform labels.

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?

Compact and front-loaded: the core action appears in the first sentence, and parameter details are backtick-formatted. No wasted words.

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

Completeness4/5

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

Complete for a simple read-only search: required query is obvious, optional parameters are explained, and an output schema exists to define returns. A brief note on when to prefer search_keyword would make it fully complete.

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?

Schema provides no descriptions (0% coverage), but the description explains source's allowed values and limit's default/max. Query's role is evident from the tool name and first sentence.

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?

Opens with a specific verb and resource: 'Meaning-based search over the user's past messages.' This distinguishes it from sibling search_keyword by modality and from get_context by scope.

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 says to use when get_context isn't enough, with a concrete example (something specific from before). It doesn't explicitly contrast with search_keyword, but the 'meaning-based' framing implies the choice.

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

All Vilix AI tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Most tools map cleanly to distinct resource+action pairs: projects, tasks, skills, user rules, memory, and messaging are all clearly separated. The main ambiguity is update_task versus update_task_state, since update_task can also change state and plan_status, though the descriptions do point to the narrow intended use.

Naming Consistency4/5

The naming is largely consistent verb_noun snake_case: create_project, update_skill, delete_task, list_projects, get_context, save_turn. Minor deviations include recent_messages lacking a verb, remove_user_rule versus delete_* style, and singular user_rule in mutations versus plural user_rules in listing.

Tool Count2/5

With 27 tools, the server is over the typical well-scoped MCP range, even though it covers several domains. Some consolidation is possible, such as folding update_task_state into update_task and reducing the overlapping retrieval/search tools.

Completeness4/5

The tool set provides strong lifecycle coverage for projects, tasks, skills, and user rules, plus memory retrieval, agent messaging, and onboarding help. Minor gaps exist, like no standalone get_task or list_tasks and no explicit inbox listing, but get_project and get_context largely cover those needs.

Resources

Need Help?