Skip to main content
Glama
io.github.avaazquezz/mcp-qdrant

io.github.avaazquezz/mcp-qdrant

by avaazquezz

Get Qdrant points by id

qdrant_points_get
Read-onlyIdempotent

Retrieve specific points by ID from a Qdrant collection, optionally including selected payload fields or vectors. Unknown IDs are omitted, so missing points do not raise errors.

Instructions

Retrieve points by id; unknown ids are simply omitted, not an error.

    Fails only if the collection itself doesn't exist. `with_payload` takes
    `true`/`false` or a list of keys to return only those (e.g. `["title"]`).

    Example: {"collection_name": "docs", "ids": [1, 2], "with_payload": ["title", "url"]}
    

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": {
      "collection_name": "<collection_name>",
      "ids": "<ids>"
    },
    "name": "qdrant_points_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
with_payloadNo
with_vectorsNo
collection_nameYes

Output Schema

NameRequiredDescriptionDefault
pointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.12.0
    • addedInput schema / properties / with_payload / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • removedInput schema / properties / with_payload / type
      Removed value: -"boolean"
  2. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: unknown ids are silently omitted rather than erroring, and the only failure mode is a missing collection. It says nothing about vector return behavior or result size.

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?

Short and front-loaded, with the most surprising fact (missing ids are not an error) first and a concrete example last. The example is close to redundant with the with_payload explanation but still clarifies composition.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and the description covers the error semantics that matter for a read. The remaining gap is with_vectors, whose default of false materially changes the response and is unmentioned anywhere.

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 description coverage is 0%, so the description carries the burden. It explains with_payload well (boolean or key list, with a concrete example) but leaves with_vectors and the int-or-string id union entirely undocumented beyond their schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource combination, 'Retrieve points by id', and the 'by id' scope implicitly separates it from qdrant_points_scroll and qdrant_query. It does not name a sibling explicitly, so differentiation is inferred rather than stated.

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 is only implied: the requirement for caller-supplied ids suggests when this is appropriate versus a scroll or query. There is no explicit when-to-use, when-not-to-use, or named alternative among the twelve sibling tools.

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