Kalpana Batch

View an image

inspect_image

Read-onlyIdempotent

Fetches one PNG, JPEG, or WebP image from a Kalpana URL (a template or asset previewUrl, or a downloadUrl from get_batch_outputs) and returns it as image content with its content type and byte size. Other hosts, other file types, and files over 5 MB are rejected, and a fetch gives up after 15 seconds. It shows one image per call; it does not build contact sheets or render templates, whose look comes from their previewUrl.

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": {
      "url": "<url>"
    },
    "name": "inspect_image"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	previewUrl or downloadUrl returned by another Kalpana tool

Output Schema

Name	Required	Description	Default
`sizeBytes`	Yes
`contentType`	Yes	MIME type of the returned image

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedOutput schema / properties / sizeBytes / maximum
```
Added value: +9007199254740991
```
First observedOct 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds the constraints an agent actually needs: a 5 MB size ceiling, a 15-second timeout, host restriction to Kalpana, and one image per call. These are non-obvious failure modes that the annotations say nothing about.

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 dense sentences, front-loaded with what is fetched and from where, then constraints, then exclusions. No filler and every clause carries operative information.

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?

For a single-URL read tool with annotations and an output schema, the description covers accepted formats, provenance of the URL, rejection rules, timeout, and scope limits. Nothing an agent needs to call it correctly is missing.

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; the description goes slightly beyond by tying the url to concrete producers (template/asset previewUrl, downloadUrl from get_batch_outputs), which helps an agent source the value. It does not add format or encoding detail beyond that.

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 concrete verb and resource ('fetches one PNG, JPEG, or WebP image') plus the exact accepted URL sources, immediately separating it from siblings like search_assets or get_batch_outputs. It also names what the tool does not do ('does not build contact sheets or render templates'), so an agent can disambiguate without opening the schema.

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?

Explicit positive case (previewUrl or downloadUrl from Kalpana tools), explicit negative cases (other hosts, other file types, >5 MB), and explicit alternatives ('whose look comes from their previewUrl'). An agent knows exactly when to call this and when to call something else.

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?