Skip to main content
Glama

sync_issues_to_vector_store

Collects MantisBT issues, computes vector embeddings and lifecycle metrics, and saves them to a local vector store for semantic search and efficiency analysis.

Instructions

Collects MantisBT issues, computes vector embeddings (local 256d or external API) and lifecycle metrics (lead time, reopens, assignment ping-pong, stagnation), and persists everything to the local mini vector store for semantic search and efficiency analysis.

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

Input Schema

NameRequiredDescriptionDefault
filter_idNoSaved filter ID in MantisBT.
max_pagesNoMaximum number of pages (50 issues/page) to index.
project_idNoFilter collection by project ID.
hydrate_individual_issuesNoIf true, fetches GET /issues/{id} individually to ensure the complete transition history.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden and does disclose the internal pipeline (fetch, embed, compute metrics, persist). However, it omits the operational traits that matter most for a write/indexing tool: whether existing vectors are replaced or appended, idempotency on re-run, expected runtime, external-API credentials/rate limits, and that hydrate_individual_issues triggers one request per issue.

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 dense sentence with the primary action front-loaded and no filler. The parenthetical enumerations of embedding modes and metric types are information-bearing, though the sentence is long enough that a reader must parse it carefully.

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 four-parameter, annotation-free mutation tool with no output schema, the description explains what it produces (a populated local vector store) but not what the caller gets back or how to verify the sync succeeded. It also leaves the relationship to the vector-search and efficiency-analysis consumers unstated, which is the main thing an agent needs to sequence calls.

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 all four parameters are already fully documented in the schema and the baseline is 3. The description adds no parameter-level meaning beyond mentioning embeddings and metrics generically; it says nothing about how max_pages or hydrate_individual_issues trade cost against completeness.

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 names a specific multi-step operation: collect MantisBT issues, compute embeddings (local 256d or external API), compute lifecycle metrics (lead time, reopens, ping-pong, stagnation), and persist to the local mini vector store. This clearly distinguishes it from read-side siblings such as search_vector_issues and list_issues, which do not write embeddings.

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 only implied through the closing phrase 'for semantic search and efficiency analysis', which hints the sync is a prerequisite for those workflows but never says so explicitly. There is no statement of when to run it versus list_issues or analyze_project_efficiency, and no note on whether it must precede search_vector_issues.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.