Skip to main content
Glama
Sign In
vivac

vivac

by JAAvila-Of
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Find nodes by their words

vivac_find
Read-only

Search all terms across node text and history, including closed nodes, to get ranked hits and lineage; optionally search other projects except private ones and show the source before using it.

Instructions

Search all terms across node text and history; closed nodes included. Returns ranked hits and lineage. everywhere crosses projects except private ones: identify the source project and show it before applying its information.

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": "vivac_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch terms; all must match.
everywhereNoSearch other projects except private ones; name/show the source before applying its information.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.22.1
    • changedInput schema / properties / everywhere / description
      Previous value: -"Searches every project on the machine rather than this one, except those that keep what they know to themselves. Say which project anything you use comes from."New value: +"Search other projects except private ones; name/show the source before applying its information."
    • changedInput schema / properties / query / description
      Previous value: -"Words to look for. Every one of them has to appear."New value: +"Search terms; all must match."
  2. Changed1 schema field changedv0.17.9
    • changedInput schema / properties / everywhere / description
      Previous value: -"Searches every project on the machine rather than this one."New value: +"Searches every project on the machine rather than this one, except those that keep what they know to themselves. Say which project anything you use comes from."
  3. First observedv0.17.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: closed nodes are included, results come back ranked with lineage, and 'everywhere' crosses projects except private ones with an obligation to identify and surface the source project before applying its information. The main omission is any sense of result volume or pagination.

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?

Two sentences, front-loaded with the search scope before the project-crossing caveat. The second sentence is a slightly compressed run-on ('everywhere crosses projects except private ones: identify the source project...'), but nothing is redundant.

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

Completeness4/5

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

With only two parameters, no output schema and read-only annotations, the description covers what is searched, what comes back (ranked hits plus lineage), and the cross-project constraint. Explaining the return payload is important here precisely because no output schema exists, and that is done at a high level.

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%, so both parameters are documented, and the description largely mirrors the schema: 'all terms must match' restates the query description, and the project-crossing caveat restates 'everywhere'. It adds a little operational framing around provenance but nothing the schema does not already say. Baseline 3 is appropriate.

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 and resource: searching node text and history, with the notable scope detail that closed nodes are included and results are ranked with lineage. An agent can tell this is a text-search tool rather than a structural retrieval tool like vivac_open, though no sibling is named for contrast.

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

Usage Guidelines3/5

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

Usage is implied by the word 'search' and the mention of what is searched, but there is no explicit when-to-use framing, no condition distinguishing it from vivac_open or vivac_why, and no statement of when it should not be used. The agent must infer the choice from the sibling names alone.

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