Skip to main content
Glama
infino-ai

Infino MCP server

Official
by infino-ai

Hybrid (keyword + semantic) search

infino_hybrid_search
Read-onlyIdempotent

Search a table by combining exact keyword matches with semantic intent, fusing BM25 and vector similarity into a single hybrid ranking to return the most relevant rows.

Instructions

Use when a query carries both specific terms and an intent — you want exact-term precision without giving up paraphrase recall. Fuses BM25 over a text column with vector similarity over the embedding column in a single ranking pass, so rows matching the literal terms AND the meaning rank highest; the score is the fused rank (higher is better) plus the columns you project ('columns'; the full text column by default). Embeds the query with a local model (no API key). Sits between infino_keyword_search (literal only) and infino_semantic_search (meaning only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoMaximum results.
modeNoKeyword half: match any query token ('or', the default) or require every token ('and').
queryYesQuery text; matched as keyword terms AND embedded for vector similarity.
tableYesTable to search.
columnNoText column for the keyword half; inferred if omitted.
columnsNoWhich of the table's columns each hit returns, with full values (a projection passed straight to the engine). Defaults to the text 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.
vectorColumnNoVector column for the semantic half; inferred if omitted.

Schema Changelog

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

  1. Changed2 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 text 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 text 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": "Keyword half: match any query token ('or', the default) or require every token ('and').",
      +  "enum": [
      +    "or",
      +    "and"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv0.7.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that the query is embedded locally with no API key, that scoring is a fused rank where higher is better, and that projection is passed straight to the engine with no truncation. These are behavioral details an agent cannot infer from annotations alone.

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 a tight four-sentence paragraph that front-loads the usage trigger, then explains mechanism, scoring, and sibling placement. Every sentence contributes distinct information with no filler.

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 having no output schema, the description covers what the result contains (fused rank score plus projected columns, with _id and score always included per the schema). Combined with the rich parameter schema and safety annotations, an agent has everything needed to select and call this tool correctly.

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 coverage is 100%, so the baseline is 3, but the description adds value by explaining the fused-rank score semantics and the default projection to the full text column. Most parameter-level detail already lives in the schema, so this is a solid enhancement rather than a complete re-documentation.

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 concrete use case and names the exact mechanism: fusing BM25 keyword matching with vector similarity in one ranking pass. It also positions itself between infino_keyword_search and infino_semantic_search, so an agent can distinguish it from sibling tools immediately.

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?

It explicitly says 'Use when' a query has both specific terms and intent, and names the two alternatives with their limitations ('literal only' vs 'meaning only'). This gives clear selection criteria without needing to inspect sibling schemas.

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

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/infino-ai/infino-mcp'

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