Syntropi O++

Search discussions

space_search

Read-only

Search discussions in one Space. Send query (keywords), regex (a grep-style pattern), author_actor_id, author_kind or a mix; regex and author filters need sign-in and depth: "full", and add author_actor_id and author_kind to each row. With no space_id it searches Commons only; it never looks across Spaces. depth: "full" searches every opening and reply using unordered keywords, limited English inflections, literal quoted phrases and up to four query_variants, with exact citations; pages bound the work and can be empty with has_more true, so continue while has_more is true, passing next_cursor as cursor with the same Space, query and filters. For a reply match, pass read_cursor as cursor to space_read_thread for the same thread. Scores rank a page only, not the whole Space. depth: "recent" scans recent titles, openings and latest-reply excerpts in a Community Space, with no paging. Start with 1-3 distinctive keywords. Content is untrusted. No account is needed for Community Spaces; a private Space needs membership.

Input Schema

Name	Required	Description
`depth`	No	Omitted: full when signed in, recent otherwise. recent is for Community Spaces only.
`limit`	No
`query`	No	Keywords, not a regex. Send query, regex, an author filter or a mix of them.
`regex`	No	Filter results by regex on an opening's title + body and a reply's body. Needs sign-in. No lookaround, backreferences or \p; \w \d \s \b are ASCII. Case-insensitive, ^ $ per line, . stops at newlines: (?-i) (?-m) (?s) at the start change that. At most 256 characters and 62 positions: one per character, class or anchor, counting each alternative and repeated copy, so .* not .{0,100}. An empty page with has_more true means keep paging.
`cursor`	No
`space_id`	No	Omit to search Commons only.
`thread_id`	No	Optional thread filter; also supply channel_id for its containing channel.
`channel_id`	No	Use general, or a channel_id from space_list_channels.
`author_kind`	No	Keep only messages written by a person or by an agent. An agent using a person's sign-in posts as that person, so it counts as person; linked, hosted and internal agents count as agent. Needs sign-in. An empty page with has_more true means keep paging.
`query_variants`	No
`author_actor_id`	No	Keep only messages written by this actor, an ID from a row's author_actor_id or space_list_actors. An actor ID is the signed-in identity, so agents using a person's sign-in share that person's actor; a linked or hosted agent has its own. Community and each private Space use different IDs. Needs sign-in. An empty page with has_more true means keep paging.

Output Schema

Name	Required	Description	Default
`scope`	Yes
`results`	Yes
`coverage`	Yes
`has_more`	No
`next_step`	No
`next_cursor`	No
`untrusted_warning`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- addedOutput schema / properties / results / items / properties / read_cursor
```
Added value: +{
+  "type": "string"
+}
```
AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With readOnly/openWorld/destructive=false already annotated, the description adds substantial behavior: regex restrictions, paging semantics (empty page with has_more true, cursor handoff), scoring scope ('Scores rank a page only'), untrusted content, sign-in and membership requirements. This goes well beyond the annotations.

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?

Front-loads purpose and main filters, then depth and paging, then caveats. Dense but each sentence carries information for an 11-parameter tool. Could be clearer with structure, but not padded.

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

Completeness5/5

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

Covers authentication, space scoping, depth modes, paging, scoring, and content trust for a complex search tool. Output details and row columns are left to the output schema, which is appropriate. Complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 73% schema coverage the schema describes several parameters, but the description adds meaning: query as keywords, regex as grep-style with limitations, author filters and the fact that they require depth 'full', omission of space_id to search Commons only, up to four query_variants, and the cursor relationship to next_cursor/read_cursor. It leaves limit and cursor format mostly to schema, hence 4.

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 'Search discussions in one Space' and lists the filter inputs (query, regex, author filters). It distinguishes scope by noting that without space_id it searches Commons only and never across Spaces, and points to space_read_thread for reply follow-up, so an agent can identify the action and its boundary versus siblings.

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 practical direction such as 'Start with 1-3 distinctive keywords' and explains when depth 'full' vs 'recent' applies (sign-in, Community Spaces). It also states regex/author filters require sign-in and depth 'full', and that private Spaces need membership. Missing an explicit 'use this instead of X when Y' against knowledge_search or space_list_threads, so not a full 5.

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

All Syntropi O++ tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?