Skip to main content
Glama
GaijinEntertainment

Pararam Nexus MCP

search_messages

Search for messages across all chats or specific chats using boolean operators, wildcards, and filters by user, date, or file type.

Instructions

Search for messages across all chats or in specific chats.

Args: query: Search query string. Supports search filters (see below) limit: Maximum number of results to return (default: 20) chat_ids: Optional list of chat IDs to search within. If None, search in all chats.

Search Syntax: Boolean Operators: By default, all terms are optional (OR), as long as one term matches. Search for "foo bar baz" finds any document containing foo OR bar OR baz.

    + (must be present) - Example: +fox (fox must be found)
    - (must not be present) - Example: -news (news must be excluded)
    Example: "quick brown +fox -news" (fox required, news excluded, quick/brown optional)

    AND, OR, NOT (also &&, ||, !) - Standard boolean operators
    NOTE: NOT takes precedence over AND, which takes precedence over OR
    Example: "(quick OR brown) AND fox"

Grouping:
    Use parentheses to group terms: "(quick OR brown) AND fox"

Wildcards:
    ? - Replace single character: "qu?ck"
    * - Replace zero or more characters: "bro*"

Strict Search:
    Use quotes for exact phrase match: "some search phrase"

Fuzziness:
    Use ~ for similar terms (Damerau-Levenshtein distance, max 2 changes):
    "quikc~ brwn~ foks~" or "quikc~1" (edit distance of 1)

Proximity Search:
    Use ~N after phrase to allow words to be N positions apart:
    "fox quick"~5 (allows up to 5 words distance, any order)

Search Filters: Format: search text /filter1 param1 param2 /filter2 param

/users or /from - Find posts by specific users
    Example: /users @user1 @user2 or /from @user1 @user2

/replyto or /reply - Find messages that are replies to specified users
    Example: /replyto @user1 @user2 or /reply @user1 @user2

/to - Find messages that mention users OR are replies to them
    Example: /to @user1 @user2

/file - Find files by name pattern
    Example: /file *filen?me*

/from_date or /after - Find posts created after a date (YYYY-MM-DD, YYYY-MM, or YYYY)
    Example: /from_date 2016-01-22 or /after 2016-01 or /after 2016

/to_date or /before - Find posts created before a date (YYYY-MM-DD, YYYY-MM, or YYYY)
    Example: /to_date 2016-01-22 or /before 2016-01 or /before 2016

/tags - Find posts containing specific tags (strict match)
    Example: /tags hey may day or /tags #hey #may #day or #hey #may #day

/has - Find posts based on content type:
    /has tag - Posts containing tags (e.g., #may)
    /has link - Posts containing URLs or markdown links
    /has email - Posts containing email addresses
    /has mention - Posts mentioning any user or user with role
    /has user - Posts containing user mentions or words starting with @
    /has group - Posts containing role mentions
    /has reply - Posts that are replies
    /has file - Posts with attached files
    /has block - Posts with text in blocks (>text or ```text)
    /has poll - Posts containing polls

Returns: ToolResponse with SearchMessagesPayload containing search results with message text, sender, chat info, and timestamp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
chat_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if operation failed
messageYesHuman-readable summary of the result
payloadNoThe actual response data
successYesWhether the operation was successful
Behavior4/5

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

With no annotations, the description carries the burden. It extensively details search behavior (operators, filters, etc.) and the return structure, but doesn't explicitly state it's read-only or mention auth/rate limits. The behavioral detail is strong.

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 lengthy but well-structured with sections for query syntax, operators, filters, and return. It is front-loaded with purpose, but some details (e.g., all operator examples) could be condensed. Still, it earns its place.

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?

Given the complexity of search with advanced syntax and filters, the description is highly complete. It covers all parameters, behavior, and return payload. No missing aspects for effective tool invocation.

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 coverage is 0%, so the description must fully explain parameters. It does so: query syntax with examples, limit default, chat_ids optional. This adds significant value 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 clearly states the tool searches for messages across all chats or specific chats. The verb 'Search' and resource 'messages' are specific, and it distinguishes from siblings like search_chats and get_chat_messages.

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 explains how to use the tool but does not explicitly guide when to use it versus alternatives like get_chat_messages. It implies usage for broad searches but lacks when-not guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GaijinEntertainment/pararam-nexus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server