remnus

search_workspace

Read-only

Search the workspace by title and content. Matches standalone pages, databases, and database rows (each row is a page) on their title or body text. Use it to locate an item before reading or updating it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum results (default 10)
`query`	Yes	Text to match against item titles and content (case-insensitive substring)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes	Matching items

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedJul 8, 2026

changedOutput schema / properties / results / items / properties / breadcrumb / description

Previous value: -"Location path from the workspace root to the item (for a database_row, ends with its parent database name)"New value: +"Path from workspace root"

changedOutput schema / properties / results / items / properties / databaseId / description

Previous value: -"Parent database ID, present for database_row results (pass to query_database)"New value: +"Present for database_row results"

changedOutput schema / properties / results / items / properties / id / description
```
Previous value: -"Item ID (pass to get_page)"New value: +"Pass to get_page"
```

changedOutput schema / properties / results / items / properties / matchedOn / description

Previous value: -"Where the query matched: title | content"New value: +"title | content"

removedOutput schema / properties / results / items / properties / parentId / description
```
Removed value: -"Parent item ID for nested sidebar items"
```
removedOutput schema / properties / results / items / properties / snippet / description
```
Removed value: -"Matching content snippet (empty when the match was on the title)"
```
removedOutput schema / properties / results / items / properties / title / description
```
Removed value: -"Item title"
```

changedOutput schema / properties / results / items / properties / type / description

Previous value: -"Item type: page | database | database_row"New value: +"page | database | database_row"

Changed9 schema fields changedJun 26, 2026

changedInput schema / properties / query / description

Previous value: -"Search query"New value: +"Text to match against item titles and content (case-insensitive substring)"

addedOutput schema / properties / results / items / properties / breadcrumb

Added value: +{
+  "description": "Location path from the workspace root to the item (for a database_row, ends with its parent database name)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / databaseId

Added value: +{
+  "description": "Parent database ID, present for database_row results (pass to query_database)",
+  "type": "string"
+}

changedOutput schema / properties / results / items / properties / id / description
```
Previous value: -"Item ID"New value: +"Item ID (pass to get_page)"
```

addedOutput schema / properties / results / items / properties / matchedOn

Added value: +{
+  "description": "Where the query matched: title | content",
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / parentId

Added value: +{
+  "description": "Parent item ID for nested sidebar items",
+  "type": "string"
+}

changedOutput schema / properties / results / items / properties / snippet / description

Previous value: -"Matching content snippet (pages only)"New value: +"Matching content snippet (empty when the match was on the title)"

changedOutput schema / properties / results / items / properties / type / description

Previous value: -"Item type (page | database)"New value: +"Item type: page | database | database_row"

changedOutput schema / properties / results / items / required

Previous value: -[
-  "id",
-  "type",
-  "title",
-  "snippet"
-]New value: +[
+  "id",
+  "type",
+  "title",
+  "breadcrumb",
+  "matchedOn",
+  "snippet"
+]

First observedJun 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, so no contradiction. Description adds value by detailing search scope (standalone pages, databases, rows) and matching behavior (title/content, case-insensitive substring), which is beyond annotations.

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 that convey purpose, scope, and usage without unnecessary words. Highly concise and front-loaded with key information.

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

Completeness4/5

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

Given annotations and output schema, the description covers core behavior and usage. Could mention pagination or result fields, but output schema fills that gap.

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 coverage is 100% with clear descriptions. The description does not add new details about parameters beyond what the schema provides, meeting baseline expectations.

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 it searches workspace by title and content, specifies matching targets (pages, databases, rows), and gives a use case. This distinguishes it from siblings like list_workspace or query_database.

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?

It provides explicit context: 'Use it to locate an item before reading or updating it.' However, it does not specify when not to use it or name alternative tools explicitly.

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

All remnus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.