Skip to main content
Glama
infino-ai

Infino MCP server

Official
by infino-ai

Semantic (vector) search

infino_semantic_search

Search by meaning, not exact wording. Embed a query locally, rank rows by vector similarity, and return paraphrases and synonyms with relevance scores.

Instructions

Use when searching for a concept by meaning and the exact wording is unknown — this retrieves paraphrases and synonyms, not just literal matches. Embeds the query with a local model (no API key) and ranks a table's embedding column by vector similarity, each hit with a score. Optional 'filter' restricts the ranking to rows whose keyword column matches a predicate first (a pushdown pre-filter, e.g. semantic search only within rows tagged 'billing'). For exact terms use infino_keyword_search; when the query has both literal terms and an intent use infino_hybrid_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoMaximum results.
queryYesQuery text; embedded and matched by vector similarity.
tableYesTable to search.
columnNoText column to return with each hit; inferred if omitted.
filterNoPre-filter: rank the kNN only among rows whose FTS 'column' matches 'query' (a pushdown pre-filter, not a post-filter on the results).
columnsNoColumns 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.
vectorColumnNoVector column to search; inferred if omitted.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the local embedding model (no API key), vector-similarity ranking, per-hit scores, and the filter's pushdown pre-filter behavior. It does not explicitly state that the operation is read-only or describe error cases, but for a search tool the disclosed behavior is substantive.

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?

Four dense, front-loaded sentences cover use case, mechanism, filter semantics, and alternatives. No filler or repetition—every sentence 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 7 parameters, a nested filter object, and no output schema, the description is remarkably complete: it explains purpose, matching behavior, scoring, filter semantics, and sibling-tool boundaries. The remaining parameter details are fully covered by the 100% schema description.

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. The description adds meaningful semantics for 'filter' (pushdown pre-filter, example with 'billing') and clarifies that 'query' is embedded for vector matching. This goes beyond the schema while not over-explaining what is already documented.

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 uses a specific verb ('search by meaning', 'retrieves paraphrases and synonyms') and clearly identifies the resource (a table's embedding column). It distinguishes semantic search from keyword and hybrid search by explaining the conceptual matching behavior, so it fully differentiates from sibling tools.

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?

The description opens with explicit when-to-use guidance ('Use when searching for a concept by meaning and the exact wording is unknown') and names exact alternatives: infino_keyword_search for exact terms and infino_hybrid_search for mixed literal+intent queries. This is model-guidance gold.

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

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