Skip to main content
Glama

search_facts

Search structured long-term facts across all connected agents; filter by category or source agent to retrieve relevant shared memory.

Instructions

Search structured long-term facts across all connected agents.

Uses multi-path hybrid retrieval (FTS5 + jieba + Jaccard + HRR + optional embeddings + entity graph). Optionally filter by category or source_agent (e.g. "claude-code", "cursor").

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_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
categoryNo
source_agentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the hybrid retrieval stack (FTS5, jieba, Jaccard, HRR, embeddings, entity graph), which tells an agent results are ranked rather than exact-matched, but it says nothing about permissions, latency, index freshness, or how the default limit of 5 affects recall.

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?

Three short lines, front-loaded with the core action before the retrieval detail. The retrieval-stack sentence is jargon-dense but earns its place as a signal about result quality; nothing is redundant.

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?

The tool has four parameters, no annotations, and an output schema (so return values need not be described). The description covers purpose and two of the three optional filters but omits limit behavior, which leaves the definition adequate rather than complete.

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 0%, so the description must compensate. It clarifies category and source_agent (with concrete example values like "claude-code", "cursor"), but never explains the limit parameter's role or its default of 5, leaving one of four parameters undocumented.

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?

"Search structured long-term facts across all connected agents" gives a specific verb (search) and resource (long-term facts) with scope (all connected agents). It implicitly distinguishes itself from list_facts by framing this as query-driven retrieval, though it never names a sibling.

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 explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The only usage signal is the optional category/source_agent filtering, which an agent could infer but which is not framed as selection guidance.

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