Skip to main content
Glama

ninerouter_generate_image

Generate or edit images from text prompts using a selected 9Router model, with configurable size, quality, count, and response format for downstream use.

Instructions

Generate or edit an image using the selected 9Router model.

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

Input Schema

NameRequiredDescriptionDefault
nNo
sizeNo
modelYes
promptYes
streamNoRequest upstream image SSE events when supported.
optionsNoAdditional fields supported by the selected 9Router endpoint.
qualityNo
response_formatNourl

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds no behavioral context such as cost implications, rate limits, output handling, or what changes when editing; it merely restates the operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of waste, but it is under-specified for a tool with eight parameters. It is concise without being helpful enough, so structure is adequate but the content is too sparse.

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

Completeness2/5

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

Given eight parameters, a nested options object, no output schema, and image generation/editing complexity, the description is far from complete. It omits return format, edit behavior, model selection, and parameter guidance that an agent needs to invoke the tool correctly.

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

Parameters2/5

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

Schema description coverage is only 25%, so the description must compensate but does not. It mentions the 'selected 9Router model' but says nothing about prompt, n, size, quality, response_format, stream, or the nested options object, leaving most parameters unexplained.

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 names a specific verb and resource: 'Generate or edit an image,' which clearly distinguishes it from siblings like chat, video, or audio tools. It adds that generation uses the selected 9Router model, but it does not explicitly differentiate from sibling alternatives beyond the image resource.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use this tool instead of alternatives, or when to choose generate versus edit. An agent must infer usage from the resource name alone; there are no exclusions, prerequisites, or model-selection tips.

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