Skip to main content
Glama
Sign In
stigmergy

stigmergy

by sturlese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_brain

Search ACL-visible team knowledge using hybrid ranking to return relevant pages instead of every match. Use for relevance questions; use list_pages to enumerate kinds, periods, or connections.

Instructions

Search ACL-visible team knowledge with hybrid ranking: the most similar pages, not every match. To enumerate a kind, a period, or a connection, use list_pages.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
filtersNo
max_resultsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose two important traits: results are permission-scoped (ACL-visible) and ranked rather than exhaustive (returns 'the most similar pages, not every match'), which tells the agent the result set is truncated by relevance. It does not say how many results come back by default, whether ranking is recalibrated when filters apply, or what happens on zero matches.

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?

Two sentences, zero filler, and the most decision-relevant information (scope plus non-exhaustive ranking) is front-loaded ahead of the sibling redirect. Every clause earns its place.

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-value explanation is rightly omitted, and the ranking/reach semantics are covered. But with no annotations and a completely undocumented free-form 'filters' parameter, the definition is not complete enough for an agent to use the tool to its full extent; the filters contract and the max_results default behavior are missing.

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 0% across three parameters, and the description compensates almost nothing: 'query' is only implied by the word 'Search', while 'filters' (a free-form object with additionalProperties) and 'max_results' are never mentioned. An agent has no way to know what the filters object accepts, which is a serious usability gap for a low-coverage schema.

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?

States a specific verb and resource ('Search ... team knowledge') and immediately qualifies scope with 'ACL-visible' and the ranking model ('hybrid ranking: the most similar pages, not every match'). It also names the sibling it is not (list_pages), so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-not rule: for enumerating a kind, a period, or a connection, use list_pages. It also implies the retrieval posture (top-ranked matches, not exhaustive). It does not address the other closely related siblings such as ask or describe_entity, which likely overlap with semantic search, so it stops short of full routing guidance.

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