Skip to main content
Glama
Sign In
hebbian-mind-enterprise

hebbian-mind-enterprise

by For-Sunny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

faiss_search

Search external FAISS index for semantically similar items to a query and retrieve top matches.

Instructions

Search external FAISS tether for semantic similarity search (if enabled).

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query
top_kNoNumber of results (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the tool performs semantic similarity search but does not disclose behavioral traits such as what happens when FAISS is disabled, whether it is read-only, or any performance implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, conveying the core action and context efficiently.

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?

Despite having only 2 parameters and no output schema, the description omits essential details like the format of results (e.g., returns similar items with scores), prerequisites for enabling FAISS, or error handling. This leaves an agent underinformed.

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?

Input schema covers 100% of parameters with basic descriptions. The description adds no additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 clearly states the tool searches an external FAISS tether for semantic similarity search, with a conditional 'if enabled'. This verb-resource pair is specific and distinguishes it from siblings like faiss_status or get_related_nodes.

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?

The description only mentions 'if enabled' but provides no guidance on when to use this tool versus alternatives like get_related_nodes or query_mind. No explicit context or exclusion criteria.

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