Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Vault Search

delimit_vault_search
Read-onlyIdempotent

Search vault entries by keyword to retrieve stored knowledge artifacts. Use this read-only tool to find matching long-term information.

Instructions

Search vault entries by query string (Pro).

When to use: to retrieve stored vault content matching a search string. The vault holds long-lived knowledge artifacts. When NOT to use: for conversation memory (use delimit_memory_search) or to capture state (delimit_vault_snapshot).

Sibling contrast: delimit_memory_search hits the conversation memory store; this hits the vault — different storage, different semantics.

Side effects: read-only on the vault backend; gated by require_premium. Calls backends.vault_bridge.search.

Prerequisite: requires Delimit Pro. An unlicensed call returns {"error": ..., "upgrade": "https://delimit.ai/pricing"} without running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.7.9
    • changedInput schema / properties / query / description
      Previous value: -"Search query for vault entries."New value: +"Search query string. Required."
  2. Changed1 schema field changedv4.5.5
    • addedInput schema / properties / query / description
      Added value: +"Search query for vault entries."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark readOnly/idempotent/non-destructive, and the description adds meaningful behavior beyond them: read-only backend, Pro license gate, internal backend call, and the exact unlicensed error/upgrade response. No contradiction with annotations.

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?

Well organized with scannable sections and front-loaded purpose; only minor redundancy remains ('Pro', 'gated by require_premium', and the prerequisite section all state the same requirement).

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

Completeness5/5

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

Covers use cases, exclusions, sibling contrast, side effects, licensing prerequisite, and unlicensed behavior; output schema exists so return-value detail is not required. Nothing needed to invoke correctly is missing.

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?

Single query parameter is fully documented by the schema (100% coverage), so the description need not repeat it. It adds only the high-level 'by query string' phrasing, which is adequate but no additional parameter detail beyond the schema.

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?

States a concrete action on a defined resource: 'Search vault entries by query string'. It additionally scopes the target as long-lived vault content and names the exact sibling it is not for memory, so an agent can distinguish it easily.

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

Usage Guidelines5/5

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

Explicit 'When to use' and 'When NOT to use' sections name exact alternatives: delimit_memory_search for conversation memory and delimit_vault_snapshot for state capture. Sibling contrast explains different storage and semantics. No inference required.

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