Skip to main content
Glama
Sign In
openserverless-mcp

openserverless-mcp

Official
by apache
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

action_add_milvus

Integrate a Milvus vector database into an endpoint's context, enabling vector search operations through ctx.MILVUS.

Instructions

Add Milvus vector DB connection to an endpoint's context. Provides ctx.MILVUS.

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

Input Schema

NameRequiredDescriptionDefault
endpointYesThe endpoint path: 'name' (uses v1 package) or 'package/name'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says it adds a connection and provides ctx.MILVUS, but does not mention side effects, permissions needed, error behavior, or reversibility. This is insufficient for a mutation operation.

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?

The description is a single sentence, which is concise. However, it could be slightly expanded to include usage context without losing 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?

For a simple tool with one fully-covered parameter and no output schema, the description covers the essential purpose but lacks context on when and how to use it effectively.

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?

There is only one parameter with 100% schema coverage. The description provides no additional meaning beyond the schema's description of 'endpoint'. Since coverage is high, baseline 3 applies; no extra value added.

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 clearly states the verb 'Add' and the resource 'Milvus vector DB connection' to an endpoint's context. It distinguishes itself from sibling tools like action_add_postgresql or action_add_redis by specifying Milvus.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., other action_add_* tools). There is no mention of prerequisites or scenarios where this tool should be avoided.

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