Vilix AI

search_keyword

Read-onlyIdempotent

Optional. Exact keyword / full-text search over the user's past messages. source (optional) restricts to one platform label as saved (e.g. "ChatGPT", "Claude"). limit optional (default 10, max 25).

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": {
      "query": "<query>"
    },
    "name": "search_keyword"
  }
}

Input Schema

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

Output 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.

First observedSep 5, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds useful behavioral details beyond the annotations: it clarifies the search scope ('user's past messages'), the source restriction to platform labels, and the limit default/max. These details help an agent predict behavior without contradicting the safe readOnly/idempotent hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the core purpose before parameter details. The stray 'Optional.' at the beginning is unnecessary and slightly confusing, costing it a perfect score, but the rest is efficient and earns its place.

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

Completeness3/5

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

The description covers scope and parameter semantics, and the output schema handles return values. However, it lacks guidance on choosing between search_keyword and search_semantic, and does not clarify exact matching behavior (e.g., phrase matching, substring, case sensitivity). Given the tool's simplicity, this is adequate but not complete for an agent to use it optimally.

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?

With 0% schema description coverage, the description compensates by explaining that `source` restricts to a platform label (with examples) and that `limit` defaults to 10 and maxes at 25. The `query` parameter is implicitly understood as the keyword/full-text search term, though additional details like case-sensitivity or matching semantics would strengthen it.

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 names a specific verb ('search') and resource ('the user's past messages'), and the qualifier 'Exact keyword / full-text' distinguishes it from the sibling search_semantic. Even without naming the sibling, the contrast is clear and an agent can separate the two intents.

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?

Usage context is implied by 'Exact keyword / full-text search' — an agent can infer it should be used when exact matches are desired rather than semantic similarity. However, the description does not explicitly say when to use this tool over search_semantic or recent_messages, nor does it mention any exclusions or when not to use it.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?