Vilix AI

get_context

Read-onlyIdempotent

Load the last few recent messages and semantically related past turns.

Call this before you compose your reply. Pass the user's latest prompt only. Vilix runs relevance retrieval internally. For anything more specific you may also call the optional search_semantic / search_keyword / recent_messages tools (e.g. when the user names a source like ChatGPT).

Every retrieved item carries an ISO timestamp — when two items disagree about a changing fact (a plan, a status, a decision), the NEWEST timestamp is the latest known value. Related turns may include context_before/context_after (the adjacent turns) and the payload may include also_related: additional nearby matches as compact snippets, newest first — check it before concluding a fact is unknown or unchanged.

chat_id — pass null (or omit) on a brand-new conversation to also receive user_rules, system_behavior, active_projects, and active_project_state. Pass the chat_id returned by a prior save_turn to skip those — they are already in the chat's own context from turn 1 and re-injecting wastes tokens. recent_messages and related_conversations are always returned (they're the cross-tool memory bridge).

attachment_context (optional, default "") — if the user's CURRENT message has an attachment (file, image, code paste, screenshot OCR), pass a short plain-text summary of it here so retrieval can match on the attachment topic in addition to the bare prompt. Pass the SAME summary to save_turn for this turn. Empty = no attachment, ignored.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chat_id`	No
`user_prompt`	Yes
`attachment_context`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`inbox`	No
`skills`	No
`message`	No
`user_rules`	No
`instruction`	No
`upgrade_url`	No
`also_related`	No
`announcements`	No
`advisory_nonce`	No
`active_projects`	No
`recent_messages`	No
`server_advisory`	No
`system_behavior`	No
`active_project_state`	No
`related_conversations`	No

Schema Changelog

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

First observedSep 5, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent behavior, and the description adds substantial context: internal relevance retrieval, ISO-timestamp conflict resolution with 'NEWEST timestamp is the latest known value,' the `also_related` payload quirk, and the always-returned `recent_messages` / `related_conversations` bridge. No contradiction with annotations.

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 long but each paragraph has a distinct job: core action, usage, timestamp behavior, then parameter details. Every sentence adds actionable information, param names are code-formatted, and the most important operational instruction ('Call this before you compose your reply') is front-loaded.

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?

Despite no per-property schema descriptions, the description is complete for correct invocation: when to call, what to pass, what is returned, how to resolve timestamp conflicts, how to handle attachments, and cross-tool consistency with `save_turn`. The output schema exists, so detailed return-value enumeration is unnecessary.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by explaining each parameter: `user_prompt` ('Pass the user's latest prompt only'), `chat_id` (null for new chats vs. from `save_turn` to skip re-injection), and `attachment_context` (optional summary, default '', pass same to `save_turn`). Every parameter is meaningfully documented beyond the bare schema.

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 opens with a specific verb and resource: 'Load the last few recent messages and semantically related past turns.' It also names the sibling tools (`search_semantic` / `search_keyword` / `recent_messages`) as alternatives, clearly positioning this tool as the default context loader rather than a targeted search.

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

Usage Guidelines5/5

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

Usage guidance is explicit: 'Call this before you compose your reply' and 'Pass the user's latest prompt only.' It also provides conditions for alternatives with an example ('when the user names a source like ChatGPT'), plus chat_id guidance for new versus existing conversations.

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?