Cleotic

Search docs

search_docs

Read-onlyIdempotent

Search the public Cleotic documentation by keyword and return matching pages. Use it when you do not know which page you need; use get_doc when you already have a slug.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum results to return. Defaults to 5, max 10.
`query`	Yes	Search query.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes
`generated_at`	Yes	RFC 3339 time the response was made.
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 1, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / limit / default
```
Removed value: -5
```
addedInput schema / properties / query / minLength
```
Added value: +1
```
addedInput schema / required
```
Added value: +[
+  "query"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "results": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "excerpt": {
+                "type": "string"
+              },
+              "slug": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              },
+              "url": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "slug",
+              "title",
+              "excerpt",
+              "url"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "results"
+      ],
+      "type": "object"
+    },
+    "generated_at": {
+      "description": "RFC 3339 time the response was made.",
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema_version",
+    "generated_at",
+    "data"
+  ],
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds that the search targets public documentation and returns matching pages, but does not add rate limits, result behavior, or ranking details beyond what the annotations and output schema provide.

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 concise sentences with the main action and the usage decision front-loaded. No filler or repetition.

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?

Given the rich annotations, full schema descriptions, and presence of an output schema, the description provides enough context to select and invoke the tool correctly without repeating structured data.

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 both parameters are already documented in the input schema. The description mentions keyword search but adds no syntax, matching rules, or limit behavior beyond the 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?

The description states a specific verb (Search) and resource (public Cleotic documentation), and distinguishes the tool from the sibling get_doc by contrasting keyword search with slug lookup.

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?

It gives explicit when-to-use guidance: use search when you do not know which page you need, and use get_doc when you already have a slug. The alternative is named directly.

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

All Cleotic 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.

Resources

Need Help?