Skip to main content
Glama

Add Entry to Vector Index

add_to_vector_index
Idempotent

Adds a journal entry to the semantic search vector index, enabling later AI sessions to retrieve relevant project context.

Instructions

Add a specific entry to the semantic search vector index

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_to_vector_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idNo
project_numberNo

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
entryIdNo
successNo
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv9.1.0
    • removedInput schema / properties / project_number / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / project_number / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / project_number / type
      Previous value: -"integer"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds essentially nothing beyond the title: it doesn't say what happens when an entry is already indexed, whether the index is per-project (despite a project_number param), or whether the operation is synchronous. With annotations lowering the bar, this still adds almost no context.

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 well-formed; the problem is under-specification rather than verbosity.

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 simple with two scalar params. However, missing parameter documentation and absent routing guidance against a near-duplicate sibling leave real gaps for an indexing mutation.

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?

Both parameters, 'entry_id' and 'project_number', have zero schema description coverage, and the description only vaguely gestures at 'a specific entry'. It never explains the accepted number-vs-string types, whether project_number selects the index scope, or why neither parameter is marked required. With 0% coverage the description needs to compensate and does not.

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?

The description gives a specific verb ('Add') and resource ('entry to the semantic search vector index'), so the action is unambiguous. It does not differentiate from the near-identical sibling 'team_add_to_vector_index' or explain its relationship to 'rebuild_vector_index', so it falls short of a 5.

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 guidance on when to call this versus 'team_add_to_vector_index', 'rebuild_vector_index', or the normal 'create_entry'/'update_entry' paths. The agent must infer whether indexing is automatic or manual, and no prerequisites or exclusions are stated.

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