Skip to main content
Glama
Sign In
FishClaw MCP

FishClaw MCP

by TnoobT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

generate_image_prompt

Read-only

Generates English image prompts in cyberpunk or tech style for a given technical topic, ready to be used directly by image generation tools.

Instructions

根据技术主题生成适合图像生成模型的英文提示词（赛博朋克/科技感风格）。 生成结果可直接传入 generate_image 工具使用。

Args: topic: 技术主题，如"AIGC"、"Python爬虫"、"区块链"等。

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": {
      "topic": "<topic>"
    },
    "name": "generate_image_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true. Description adds that output is ready for generate_image, indicating non-destructive generation. No contradictions. Adds useful style and compatibility context.

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 concise paragraphs: first explains purpose and output usage, second explains parameter. No wasted words, well-organized, front-loaded with key info.

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

Completeness4/5

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

Tool is simple with one param. Description covers purpose, parameter, and output usage. Output schema exists, so return format need not be detailed. Adequate for the task.

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?

Only parameter 'topic' has 0% schema description coverage. Description compensates by explaining topic as technical subject and providing examples (AIGC, Python爬虫, etc.), adding significant semantic value.

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?

Description clearly states the tool generates English image prompts for tech topics in cyberpunk/tech style, and specifies output can be directly used with sibling generate_image tool. Differentiates from generate_image (image generation) and other siblings.

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?

Implies usage for creating prompts to feed into generate_image, but lacks explicit when-not-to-use or mention of alternatives. Clear enough for typical use case.

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

Deploy Server

Other Tools