VectorSmith
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QDRANT_URL | Yes | The URL of your Qdrant cluster. This is required to connect to the vector database used by VectorSmith. | |
| QDRANT_API_KEY | No | Optional API key for authenticating with your Qdrant cluster. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_available_toolsA | Live VectorSmith catalog from the current tools.yaml, including tools saved after this chat started. Claude Desktop freezes the named connector list at connect — call this before saying a tool is missing, then invoke with run_tool. |
| run_toolA | Run any VectorSmith tool by name with its arguments from list_available_tools. Use this for tools added to tools.yaml after Claude connected; Desktop will not show those names in the connector list. Arguments are re-validated against that tool's compiled inputSchema (types, enums, limits); hidden static_filters and request tenancy still apply. Not a bypass. |
| search_invoicesA | Search invoices by free text and filter by client, status, or amount. Use when the user asks about invoices, billing, or payments. |
| get_invoiceA | Fetch one invoice by invoice_id (for example INV-0001). Use when the user already has the invoice number. |
| count_invoicesA | Count invoices matching optional client and status filters. Use when the user asks how many invoices there are. |
| list_overdue_invoicesA | List overdue invoices only, optionally filtered by client or minimum amount. Use when the user asks which invoices are overdue or past due. |
| search_paid_invoicesA | Search invoices that are already paid, optionally by client or amount. Use when the user asks about paid invoices or completed payments. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
get_invoice, count_invoices, and the meta discovery/execution tools are distinct, though run_tool is a catch-all that could execute any of the invoice tools. The real ambiguity is that search_invoices already supports status filtering, making search_paid_invoices and list_overdue_invoices overlapping subsets. The use-when guidance helps, but an agent could reasonably pick either general or specialized tools for paid/overdue queries.
All tool names follow a predictable snake_case verb_noun pattern: search_invoices, get_invoice, count_invoices, list_overdue_invoices, search_paid_invoices, run_tool, and list_available_tools. The meta tools do not break the convention, so naming is consistent across the set.
Seven tools is well within the ideal scope, with two infrastructure tools for dynamic discovery/execution and five read-only invoice tools. Each tool has a reasonable purpose, and the count does not feel bloated or thin.
The read-only invoice workflow is well covered: search, get by ID, count, overdue list, and paid search. It lacks create/update/delete operations and an explicit 'list all invoices' tool, but search with filters can work around the latter, and the descriptions imply a query/reporting focus.