Skip to main content
Glama

search_vector_issues

Search MantisBT issues semantically by cosine similarity and metadata filters to find recurring bugs, similar root causes, or technical history.

Instructions

Runs a semantic search by cosine similarity over the MantisBT issue mini vector store, combining embeddings and metadata filters to find recurring bugs, similar root causes or technical history.

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

Input Schema

NameRequiredDescriptionDefault
queryYesNatural-language semantic query (e.g. 'timeout in the payment queue').
top_kNo
handler_idNo
project_idNo
min_similarityNo
only_unresolvedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description has to carry behavioral disclosure. It usefully states that this is a cosine-similarity semantic search combining embeddings with metadata filters, but it omits whether the operation is read-only, whether the vector store must be synced first, and what result behavior to expect.

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?

The definition is a single front-loaded sentence with no obvious filler, and it efficiently combines the search method, data source, and intended use cases. It is dense but readable, though it lacks a more structured breakdown of usage constraints.

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

Completeness2/5

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

For a six-parameter search tool with no annotations and no output schema, the description is incomplete. It does not explain prerequisites such as vector-store synchronization, return behavior, pagination, or the roles of most parameters.

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?

Schema description coverage is only 17%, so the description should compensate by explaining the six parameters. It vaguely refers to metadata filters, but does not clarify handler_id, project_id, top_k, min_similarity, or only_unresolved, leaving most parameter meaning to undocumented schema fields.

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 states a specific verb and resource: semantic search by cosine similarity over the MantisBT issue vector store. It also gives concrete use cases such as recurring bugs and similar root causes, though it does not explicitly differentiate this from siblings like list_issues or keyword search.

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?

The stated use cases imply when to use it: finding semantically similar issues, recurring bugs, or related technical history. However, there is no explicit when-not guidance, no mention of needing a synced vector store, and no comparison to alternative tools.

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