tela

Overview Schema Source Related Servers Discussions Admin

Search

search

Read-only

Find wiki pages by exact keyword, identifier, or error string with ranked full-text results and highlighted snippets. Works without an embedder.

Instructions

Keyword (full-text) lookup over title + body, ranked + snippet-highlighted. Use to find a page you can name or that contains an exact term/identifier/error string. Works WITHOUT an embedder (always available). Optional space_id narrows to one space. To answer a question or gather material on a topic by meaning, use research instead.

Input Schema

Name	Required	Description
`limit`	No	max results (default 25)
`query`	Yes	search terms
`space_id`	No	optional space id to restrict results to

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.11.0Oct 15, 2026

addedOutput schema / properties / results / items / properties / public
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / results / items / properties / public_path
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / results / items / required

Previous value: -[
-  "page_id",
-  "space_id",
-  "title",
-  "snippet",
-  "breadcrumb",
-  "url",
-  "id",
-  "text"
-]New value: +[
+  "page_id",
+  "space_id",
+  "title",
+  "snippet",
+  "breadcrumb",
+  "public",
+  "url",
+  "id",
+  "text"
+]

First observedv0.1.0Jul 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnly/destructive/openWorld, but the description adds genuine behavioral context beyond them: results are ranked and snippet-highlighted, and the tool 'works WITHOUT an embedder (always available)', which tells the agent about availability guarantees. It does not mention pagination or result-cap behavior, so a 4 rather than 5.

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-loaded with the mechanism before usage and the alternative. All content is relevant, though the parenthetical '(always available)' and the embedder clause make the third sentence slightly denser than needed.

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?

An output schema exists, so return-value explanation is unnecessary. The description covers what the tool searches, when to prefer it, how to narrow scope, and the key availability caveat — complete for a read-only search tool of this complexity.

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 100%, so all three parameters are already documented in the schema. The description restates that space_id narrows to one space but adds no syntax, format, or ranking-tuning detail beyond what the schema provides — baseline 3.

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 mechanism (keyword/full-text lookup over title + body) with concrete output behavior (ranked, snippet-highlighted). It explicitly contrasts itself with the `research` sibling by meaning vs. exact-term matching, so an agent can discriminate without opening schemas.

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

Usage Guidelines5/5

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

Gives a clear when-to-use ('find a page you can name or that contains an exact term/identifier/error string') and an explicit when-not with the named alternative ('to answer a question or gather material on a topic by meaning, use research instead'). Nothing is left to inference.

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