Kognai Kreativ: images and short videos by agents

Make an image

make_image

One original image from a text prompt, made by Kreativ agents and checked by a quality reviewer before delivery. Answers with the order id and a result link. Paid per call over x402 in USDC on Base or Solana; on Base the payment is collected only on delivery. Real faces, children and nudity are refused before any payment.

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": {
      "prompt": "<prompt>"
    },
    "name": "make_image"
  }
}

Input Schema

Name	Required	Description	Default
`aspect`	No	the frame: square, portrait or landscape	1:1
`prompt`	Yes	what it should show, in plain words

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavior: the image is made by agents and checked by a quality reviewer, the response includes an order id and result link, billing occurs per call over x402 in USDC on Base or Solana, Base payment is collected only on delivery, and forbidden content is refused before payment. This is unusually rich operational context for a generation 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 compact and front-loaded: purpose first, then output shape, payment model, and content restrictions. Every sentence adds useful information without redundancy.

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 two-parameter, no-output-schema tool, the description covers the essential missing context: what is returned, how payment works, the review step, and content refusal rules. The remaining parameter details are already fully covered by the input schema.

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 100%, and the schema already documents both prompt and aspect, including the enum and defaults. The description reinforces that the tool takes a text prompt but adds no additional syntax, constraints, or aspect-ratio guidance beyond the structured schema.

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 core operation: producing one original image from a text prompt using Kreativ agents, with quality review before delivery. The resource and output are specific, though sibling differentiation from make_video or get_order is only implicit through the word 'image' and the mention of an order id.

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 provides clear context for when to use the tool: generating an original image from a text prompt, with explicit content exclusions for real faces, children, and nudity, plus payment conditions. It does not explicitly route the agent to or away from sibling tools such as make_video, so this is strong but not fully explicit alternative guidance.

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

All Kognai Kreativ: images and short videos by agents 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?