Wraps

Search Wraps docs

search_docs

Read-only

Search the full Wraps documentation (CLI, TypeScript SDKs, infrastructure, guides) and return the matching sections as markdown. Use this first for any 'how do I ... with Wraps' question.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum sections to return (default 5).
`query`	Yes	Words to search for, e.g. 'verify domain', 'send batch', 'bounce handling'.

Output Schema

Name	Required	Description	Default
`query`	Yes	The query as searched.
`matches`	Yes	Empty when nothing matched; that is a result, not an error.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "matches": {
+      "description": "Empty when nothing matched; that is a result, not an error.",
+      "items": {
+        "properties": {
+          "excerpt": {
+            "description": "Truncated section body.",
+            "type": "string"
+          },
+          "heading": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "heading",
+          "excerpt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "description": "The query as searched.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "query",
+    "matches"
+  ],
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and non-open-world, and the description adds useful context: it searches the full corpus rather than a single known document and returns markdown sections. It does not discuss edge behavior around limits or empty results, but with annotations and an output schema, the remaining burden is low.

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?

A single front-loaded sentence states the action, scope, and output, followed by one short usage directive. There is no filler, repetition, or unnecessarily long detail.

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?

With only 2 simple params, a fully documented schema, an output schema present, and read-only annotations, the description covers what an agent needs to decide when to call it. The usage directive and scope statement fill the remaining selection context.

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 the input schema already fully documents query and limit with examples and a default. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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?

Description names a specific verb ('Search'), a clear resource ('the full Wraps documentation'), enumerates the coverage ('CLI, TypeScript SDKs, infrastructure, guides'), and states the output form ('matching sections as markdown'). This distinguishes it from siblings like get_doc/list_docs, which imply fetching or listing individual docs.

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?

The phrase 'Use this first for any "how do I ... with Wraps" question' gives an explicit when-to-use trigger for an agent. It does not name exclusion conditions or alternative tools (e.g., get_doc for a known doc), so it misses the 'when-not' half of ideal guidance.

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

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