Skip to main content
Glama
Sign In
imagine-mcp

imagine-mcp

by n24q02m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Help

help
Read-onlyIdempotent

Get full documentation on understanding, generating, and configuring image and video tools across multiple AI providers.

Instructions

Full documentation. Topics: understand | generate | config.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "help"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNounderstand

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.0
  2. Removedv1.10.1
  3. First observedv1.8.1

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and non-open-world, so the safety profile is fully covered. The description adds nothing beyond what the annotations provide — no note on output size, truncation, or how the documented topics relate to the sibling tools.

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 terse fragments, front-loaded with the purpose and then the option set. No sentence is wasted.

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?

With an output schema present, return values need no explanation, and there is only one optional parameter. The description covers the topic set adequately, but it never links those topics to the sibling tools an agent is choosing between, which is the main remaining gap.

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 description coverage is 0% and the schema types the topic as a bare string with no enum, so the description's enumerated values ('understand | generate | config') are the only place the valid topic set is documented. It adds real meaning over the schema, though it omits the default and what each topic covers.

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?

States a specific verb+resource: it returns 'full documentation' scoped by topic. The topic list maps directly onto the sibling tool names (understand, generate, config), which lets an agent connect this helper to those tools, though it never says so explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: listing 'understand | generate | config' as topics hints that an agent calls help to learn about those siblings, but there is no stated when-to-use, no when-not-to-use, and no explicit routing to an alternative.

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