Robert Blust

search

Find entities by words, substring or exact name. match: "words" needs every query word's stem in name, tagline, fields, sections or cells; "text" (default) is a case-insensitive substring over the same; "name" the exact canonical name. Optional type, owner, limit, cursor. Returns results with id, title, type, matched, words in words mode, and page: a listing, not a ranking.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No
`limit`	No	Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
`match`	No
`owner`	No	An owner's id, to keep its entities
`query`	Yes
`cursor`	No	`page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`match`	Yes
`model`	Yes
`query`	Yes
`words`	No
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 23, 2026

changedInput schema / properties / match / enum

Previous value: -[
-  "text",
-  "name"
-]New value: +[
+  "text",
+  "name",
+  "words"
+]

changedOutput schema / properties / match / enum

Previous value: -[
-  "text",
-  "name"
-]New value: +[
+  "text",
+  "name",
+  "words"
+]

addedOutput schema / properties / words

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "common": {
+        "type": "boolean"
+      },
+      "stem": {
+        "type": "string"
+      },
+      "word": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "word",
+      "stem",
+      "common"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed2 schema fields changedSep 21, 2026

addedInput schema / properties / cursor / description

Added value: +"`page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page."

addedInput schema / properties / limit / description

Added value: +"Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200."

Changed11 schema fields changedSep 21, 2026

addedInput schema / properties / cursor
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / limit

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / match

Added value: +{
+  "enum": [
+    "text",
+    "name"
+  ],
+  "type": "string"
+}

addedInput schema / properties / owner

Added value: +{
+  "description": "An owner's id, to keep its entities",
+  "type": "string"
+}

addedInput schema / properties / type
```
Added value: +{
+  "type": "string"
+}
```
changedOutput schema / additionalProperties
```
Previous value: -{}New value: +false
```

addedOutput schema / properties / match

Added value: +{
+  "enum": [
+    "text",
+    "name"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / page

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "hasMore": {
+      "type": "boolean"
+    },
+    "nextCursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "returned": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "total": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "hasMore",
+    "nextCursor"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / query
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / results

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "matched": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "key": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "where": {
+              "enum": [
+                "name",
+                "tagline",
+                "field",
+                "section",
+                "table"
+              ],
+              "type": "string"
+            }
+          },
+          "required": [
+            "where",
+            "key"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "owner": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tagline": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "url": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "title",
+      "type",
+      "owner",
+      "tagline",
+      "url",
+      "matched"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "model"
-]New value: +[
+  "query",
+  "match",
+  "results",
+  "page",
+  "model"
+]

First observedSep 17, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the page is a listing, not a ranking, and describes the return fields. However, it does not state whether the operation is read-only, any side effects, or authentication requirements, which are important for an agent.

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?

The description is dense but well-structured, front-loading the purpose and then efficiently covering match modes, optional parameters, and return fields. Every sentence adds value, though it could be slightly more streamlined.

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

Completeness3/5

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

The description covers match semantics, return structure, and the listing-not-ranking behavior. However, it omits an explanation for the 'type' parameter and does not provide usage guidance versus siblings. Given the output schema exists, the return is covered, but the missing type semantics and lack of when-to-use context make it incomplete.

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 50%. The description adds significant value for the 'match' parameter by detailing the three modes and their semantics, and it explains the return structure. However, it does not elaborate on the 'type' parameter, which lacks a schema description, leaving a gap that the description should fill.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool finds entities by words, substring, or exact name, which is a specific verb and resource. It distinguishes from siblings like list_entities and get_entity by focusing on search semantics, though it doesn't explicitly name alternatives.

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

Usage Guidelines3/5

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

The description explains the three match modes and optional parameters, giving clear context on how to use the tool. However, it does not provide explicit guidance on when to use this tool versus sibling tools like list_entities or find_evidence, nor does it state exclusions.

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

All Robert Blust 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?