Skip to main content
Glama

Kalpana Batch

by one.kalpana
OverviewDiscussionsAdmin

Find templates

search_templates
Read-onlyIdempotent

Finds the workspace's templates to fill with data, one page at a time. Each comes with its ID, pixel size, input count, previewUrl and a link that opens it in Kalpana. Without query it lists the most recently updated templates. query matches an exact template ID, or words in a name, description or campaign topic; the size and preview filters narrow further. Animated templates are included and marked isAnimated: their images show one moment of the motion. The fillable inputs are not included: get_template_inputs returns them for one ID, and inspect_image shows a previewUrl. Needs templates:read.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
limitNoResults per page (default 10); values above 20 are capped at 20
queryNoExact template UUID or name, description, or campaign topic; at least 3 characters. Omit to browse.
widthNoExact template width in pixels
heightNoExact template height in pixels
hasPreviewNoSet true to exclude templates without a preview URL

Output Schema

NameRequiredDescriptionDefault
pageYes
itemsYes
limitYesPage size actually applied
totalYesCount of all matches across every page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / height / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / width / 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 / variableCount / 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
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses pagination, default ordering, animated-template behavior, image preview limitations, excluded fillable inputs, and the templates:read permission requirement. These are exactly the behavioral details an agent needs before calling the tool.

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?

The description is front-loaded with purpose and pagination, then adds query behavior, caveats, exclusions, and permissions in a compact sequence. Every sentence earns its place and no filler is present.

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 paginated search/list tool with an output schema and full input schema coverage, the description still covers scope, default behavior, filters, return caveats, excluded data, alternative tools, and required permission. Nothing material is missing for correct invocation.

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 schema already documents the six parameters. The description adds useful semantics beyond the schema: omitting query lists recently updated templates, query matches words in names/descriptions/campaign topics, and size/preview filters narrow results.

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 and resource: it finds the workspace's templates, one page at a time. It also distinguishes this tool from get_template_inputs and inspect_image by explaining which related data it does and does not return.

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?

It gives clear conditions for browsing without a query, searching with a query, and narrowing with size and preview filters. It also routes the agent to get_template_inputs and inspect_image for data this tool omits, though it does not explicitly compare against search_assets.

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

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