Skip to main content
Glama
Sign In

ViralMint

by net.viralmint
OverviewDiscussionsAdmin

Image director

image_director
Read-only

Free (60 an hour). Writes an AI Image / AI Thumbnail prompt with the user and returns a card plus the arguments for generate_image / generate_thumbnail. Nothing is made or charged. Pass history and card back each turn.

Args: message: the user's words, 1-4000 chars. mode: image (default) | thumbnail. history: the history from the last answer (optional, max 40 turns). card: the last card, to change it (optional). aspect: 9:16 | 16:9 | 1:1 | 4:5 | 3:4 (thumbnail: 16:9 | 9:16). has_refs: true when you will pass reference_library_ids to the generate tool.

Returns: {ok, reply, card:{mode, prompt, negative, look, aspect, count, title, use_refs}|null, generate_args?:{prompt, aspect}, chips:[{label, message?, action?}], history}

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": {
      "message": "<message>"
    },
    "name": "image_director"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardNo
modeNo
aspectNo
historyNoThe conversation so far: pass back the `history` the last answer gave you.
messageYes
has_refsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond readOnlyHint: discloses the rate limit (60 an hour), that "Nothing is made or charged," the 40-turn history cap, and the state-continuity contract for history/card. It also enumerates the full return shape including the nullable card and optional generate_args, which is the agent's real integration surface.

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

Conciseness4/5

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

Front-loaded summary sentence followed by clean Args/Returns blocks, which is the right structure for a stateful tool. Minor redundancy: the char limits and enum lists duplicate what the schema already declares, costing a little space.

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?

Six parameters, nested history objects, and no output schema, so the definition carries the burden and does: it supplies the return contract, the multi-turn state protocol, and the handoff arguments for the generation tools. Nothing an agent needs before the first call or the next turn is missing.

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

Parameters5/5

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

With schema coverage at only 17%, the description compensates fully: it documents message length, mode with its default, history semantics and turn cap, card as the last card to modify, the aspect enum with the thumbnail restriction, and the conditional meaning of has_refs. The enum values and defaults are given operational meaning rather than restated.

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 specific verb and resource ("Writes an AI Image / AI Thumbnail prompt with the user") plus the concrete artifact returned ("a card plus the arguments for generate_image / generate_thumbnail"). This clearly separates it from the sibling generation tools, which it names explicitly.

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?

Establishes the workflow context: it is the drafting step whose output feeds generate_image / generate_thumbnail, and it carries a state rule ("Pass `history` and `card` back each turn") plus a free-quota note. It does not explicitly say "use generate_image to actually render," but the downstream argument output implies it clearly.

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

All ViralMint 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