Skip to main content
Glama
Infino MCP server

Infino MCP server

Official

Keyword (BM25) search

infino_keyword_search
Read-onlyIdempotent

Search a text column for literal terms such as identifiers, error codes, or exact phrases, and rank rows by BM25 relevance with scores.

Instructions

Use when the query is literal terms — identifiers, error codes, product names, exact phrases — and you want results ranked by relevance. BM25 full-text search over a text column: ranks rows by how well the query's tokens (and their stems) match, each with a relevance score (higher is better) plus the columns you project ('columns'; the full text column by default). Matches exact tokens, not synonyms or paraphrases. Prefer this over SQL LIKE for known literal terms. For meaning-based search use infino_semantic_search; for both at once use infino_hybrid_search.

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

Input Schema

NameRequiredDescriptionDefault
kNoMaximum results to return.
modeNoMatch any query token ('or', the default) or require every token ('and').
queryYesQuery terms, matched as literal tokens.
tableYesTable to search.
columnNoText column to search; inferred from the table schema when omitted.
columnsNoWhich of the table's columns each hit returns, with full values (a projection passed straight to the engine). Defaults to the searched column; '_id' and 'score' are always included. Any column works: ['id'] for compact hits at a large k, ['id', 'text'] to get the full text alongside an id to cite, ['title', 'created_at'] for metadata. Nothing is truncated; read fewer columns or a smaller k to keep results small.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.0
    • removedInput schema / properties / stats
      Removed value: -{
      -  "description": "BM25 statistics scope: 'per_superfile' (the default; each segment scored against its own statistics) or 'global' (one table-wide idf, so a table written in many small batches ranks like one corpus).",
      -  "enum": [
      -    "per_superfile",
      -    "global"
      -  ],
      -  "type": "string"
      -}
  2. Changed3 schema fields changedv0.14.0
    • changedInput schema / properties / columns / description
      Previous value: -"Columns to return with each hit (e.g. an id, path, or line range to cite). Defaults to the searched column; '_id' and 'score' are always included."New value: +"Which of the table's columns each hit returns, with full values (a projection passed straight to the engine). Defaults to the searched column; '_id' and 'score' are always included. Any column works: ['id'] for compact hits at a large k, ['id', 'text'] to get the full text alongside an id to cite, ['title', 'created_at'] for metadata. Nothing is truncated; read fewer columns or a smaller k to keep results small."
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "Match any query token ('or', the default) or require every token ('and').",
      +  "enum": [
      +    "or",
      +    "and"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / stats
      Added value: +{
      +  "description": "BM25 statistics scope: 'per_superfile' (the default; each segment scored against its own statistics) or 'global' (one table-wide idf, so a table written in many small batches ranks like one corpus).",
      +  "enum": [
      +    "per_superfile",
      +    "global"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changedv0.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observedv0.7.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already carry the read-only/idempotent safety profile, and the description adds real behavior: ranking is by BM25 token/stem match, each hit carries a relevance score where higher is better, and no synonym or paraphrase expansion occurs. It stops short of covering result-size or cost implications, which keeps it from a 5.

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?

Front-loaded with the selection criterion, then mechanism, then sibling routing — a sound order with no filler. Slight redundancy between 'literal terms' and 'Matches exact tokens, not synonyms or paraphrases' costs a point.

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?

For a read-only search tool with no output schema, the description explains what comes back (relevance score plus projected columns, with _id and score always present) and how to keep results small. Nothing an agent needs to call it correctly is missing.

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%, so k, mode, column and columns are already documented in the schema. The description restates the 'columns' projection and its default and clarifies that score is higher-is-better, but adds no new semantics such as how 'mode' interacts with ranking.

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?

States a specific verb and mechanism (BM25 full-text search over a text column) and names the exact query class it serves: identifiers, error codes, product names, exact phrases. It is clearly separable from the semantic and hybrid siblings.

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?

Gives an explicit use-when condition, names two alternatives with the condition that selects each (meaning-based -> infino_semantic_search, both -> infino_hybrid_search), and adds a comparative rule against a non-sibling (prefer over SQL LIKE).

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