Skip to main content
Glama
Sign In
wmilvus-mcp

wmilvus-mcp

by wisrovi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_wmilvus_pattern

Search a catalog of production-ready WMilvus architectural patterns for Milvus vector database applications.

Instructions

Search for production-ready WMilvus architectural patterns in the catalog.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Search' implies a non-destructive read, but nothing is said about matching behavior, result limits, ranking, or pagination; the only behavioral hint is the implicit read semantics of the verb.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity edges into under-specification rather than tightness.

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?

An output schema exists, so return values need not be explained, and the tool is a simple one-parameter search. Still, the undocumented query semantics and absent routing versus sibling retrieval tools leave meaningful gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required 'query' parameter has no description anywhere. The description does not clarify whether the query is a natural-language phrase, keyword list, pattern name, or filter expression, so the schema gap is not compensated.

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 (Search) and a specific resource (WMilvus architectural patterns) with scoping qualifier (production-ready, in the catalog). However, it does not distinguish itself from near-siblings such as get_wmilvus_architect_blueprints, leaving the search-vs-retrieve boundary ambiguous.

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 when-to-use guidance, no mention of when to prefer this over get_wmilvus_architect_blueprints or get_wmilvus_architect_manual, and no exclusions. An agent must guess which sibling to call for pattern discovery versus retrieval.

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