Kalpana Batch

Find image assets

search_assets

Read-onlyIdempotent

Finds images to put into template image inputs: the ready PNG, JPEG and WebP files under 5 MB in the workspace, one page at a time, each with a previewUrl. With no filters it lists the most recently updated images and also names every image collection (named groups of images) with its ID and image count. collection keeps one collection's images, given by its name (ignoring case) or ID: when the user says where their images are ("the Diwali photos"), pass that name. query matches file names, and both combine. A collection name that matches none is refused with the workspace's collection names. Each image comes with its pixel width and height when known. An asset's id is what an image input takes in batch rows. inspect_image shows a previewUrl, and upload_images adds the user's own files. Needs assets:read.

Input Schema

Name	Required	Description
`page`	No	Page number, starting at 1
`limit`	No	Results per page (default 8); values above 12 are capped at 12
`query`	No	Filename text to search for, 2 to 100 characters; omit to browse
`collection`	No	A collection's name (ignoring case) or ID; limits results to it

Output Schema

Name	Required	Description
`page`	Yes
`items`	Yes
`limit`	Yes	Page size actually applied
`total`	Yes	Count of all matches across every page
`collections`	No	Every image collection, when no filter is given (most recently updated first)

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 30, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / limit / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```
- removedOutput schema / properties / collections / items / properties / createdAt / $ref
```
Removed value: -"#/properties/items/items/properties/createdAt"
```
- addedOutput schema / properties / collections / items / properties / createdAt / description
```
Added value: +"Creation time, ISO 8601"
```
- addedOutput schema / properties / collections / items / properties / createdAt / type
```
Added value: +"string"
```
- addedOutput schema / properties / collections / items / properties / id / pattern
```
Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
```
- addedOutput schema / properties / collections / items / properties / itemCount / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / items / items / properties / height / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / items / items / properties / id / pattern
```
Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
```
- addedOutput schema / properties / items / items / properties / sizeBytes / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / items / items / properties / width / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / limit / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / page / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / total / maximum
```
Added value: +9007199254740991
```

Changed2 schema fields changedOct 26, 2026

addedOutput schema / properties / items / items / properties / height

Added value: +{
+  "description": "Pixel height",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / items / items / properties / width

Added value: +{
+  "description": "Pixel width; left out when the file does not say",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

Changed3 schema fields changedOct 24, 2026

addedInput schema / properties / collection

Added value: +{
+  "description": "A collection's name (ignoring case) or ID; limits results to it",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / collectionId

Removed value: -{
-  "description": "Collection ID from list_asset_collections; limits results to that collection",
-  "format": "uuid",
-  "type": "string"
-}

addedOutput schema / properties / collections

Added value: +{
+  "description": "Every image collection, when no filter is given (most recently updated first)",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "createdAt": {
+        "$ref": "#/properties/items/items/properties/createdAt"
+      },
+      "description": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "collectionId for search_assets",
+        "format": "uuid",
+        "type": "string"
+      },
+      "itemCount": {
+        "description": "Number of images in the collection",
+        "minimum": 0,
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "description",
+      "itemCount",
+      "createdAt"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the eligibility constraints (ready files, under 5 MB), pagination ("one page at a time"), the default ordering, the previewUrl and pixel dimensions returned, and the error behavior when a collection name matches nothing (refusal listing workspace collection names). It also states the required scope, assets:read.

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 purpose and default behavior, and nearly every sentence carries distinct information. It is a dense single paragraph, though, and the filter semantics could be broken out for faster scanning.

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?

Covers everything needed to call it correctly: default behavior, filter semantics, pagination, error handling, required scope, and the returned identifiers used by image inputs in batch rows. An output schema exists, yet the description still surfaces the fields an agent must act on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: `collection` accepts a user-spoken name (case-insensitive) or ID and how to source it from conversation, `query` matches file names, and the two filters combine. It does not add anything for `page`/`limit` beyond the schema, keeping it short of a 5.

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?

Opens with a specific verb+resource plus its purpose: "Finds images to put into template image inputs", narrowed to ready PNG/JPEG/WebP files under 5 MB. That framing makes it clearly distinct from siblings like inspect_image and upload_images, which it also names.

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?

States the no-filter default (most recently updated images plus collection listing), when to pass `collection` ("when the user says where their images are"), and that `query` and `collection` combine. It also routes to inspect_image for previews and upload_images for adding files, so alternatives are explicit.

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

All Kalpana Batch 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?