Skip to main content
Glama
Sign In
qmcp

qmcp

by BigKAA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

qdrant_get_collection_info

Retrieves information about a named Qdrant collection, enabling you to inspect its status and settings before running semantic search queries.

Instructions

Get information about a collection.

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": {
      "name": "<name>"
    },
    "name": "qdrant_get_collection_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCollection name

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies a safe read via the word 'Get'. It does not state whether the call can fail on a missing collection, whether it is side-effect free, or what kind of metadata it exposes, leaving the agent to guess.

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?

A single short sentence with no wasted words, and the resource is front-loaded. It is efficient but so thin that the brevity comes at the cost of information rather than being disciplined conciseness.

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

Completeness3/5

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

The tool is simple (one required parameter) and an output schema exists, so return values need not be described. Still, with no annotations and numerous similarly-named metadata siblings, the description should explain what 'information' covers and how it differs from qdrant_get_status and qdrant_diagnose_collection.

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 100% and the single parameter 'name' is documented as 'Collection name', so the schema does the work. The description adds nothing beyond that, which is acceptable at the baseline for a one-parameter tool.

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

Purpose3/5

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

The description names a specific verb and resource (get information about a collection), which is clear enough to know it is a read operation on collection metadata. However, 'information' is vague about what is actually returned (config, vectors, points count, status), and it does not distinguish itself from siblings such as qdrant_get_status, qdrant_diagnose_collection, or qdrant_diff_collection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus qdrant_get_status or qdrant_diagnose_collection, and no mention of prerequisites (e.g., collection must exist, permissions needed). The agent must infer usage entirely from the name.

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

Deploy Server

Other Tools