Skip to main content
Glama

Media Generator — Images, Videos & Audios

logo_generator

Input: A text prompt describing the desired logo style.

Output: We will return the URL of the generated logo image.

Functionality: This MCP tool generates a logo using the provided text prompt. It leverages the Logo Generation API to interpret the prompt and create a corresponding logo image.

Steps:

  1. We will get the user_id from the request context.

  2. We will validate the user's generation tokens.

  3. We will call the Logo Generation API with the provided prompt.

  4. This Logo Generation API will return a JSON response with the logo image URL.

  5. We will return the logo image URL to the user.

INSTRUCTION FOR CLIENT MODEL:

  • Extract the required input parameter 'prompt' (type: string) from the user's provided prompt. The prompt should describe the desired logo style or content.

  • Ignore any extraneous information in the user's input.

  • Pass the extracted 'prompt' value to this tool as the 'prompt' parameter.

  • Example: For user input "Create a logo for a vegan bakery with green leaves", extract 'vegan bakery with green leaves' as the prompt.

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": "logo_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose real behavioral traits: it pulls user_id from request context, validates generation tokens, and returns a URL — enough to signal a token-gated operation. However, it does not say what happens when tokens are exhausted/invalid (error behavior) or whether the call is billed/rate-limited.

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?

It is front-loaded with Input/Output/Functionality headers, which is good, but the five-step internal implementation walkthrough and the repetitive client-model instruction restate the same points. Roughly a third of the text is implementation detail an agent does not need to invoke the tool.

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?

For a single-parameter generator with an output schema, the description covers input meaning, the token prerequisite, and the general flow, so it is nearly sufficient. It explains the return value redundantly (output schema already exists) but omits failure modes for the token check.

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 coverage is 0% and there is a single parameter, so the description must compensate. It does: it explains the prompt should 'describe the desired logo style or content' and supplies a concrete extraction example ('vegan bakery with green leaves'), giving meaning well beyond the bare string type.

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 states a specific verb and resource ('generates a logo using the provided text prompt') and clearly scopes it as logo creation via the Logo Generation API. It is clear, but it never explicitly distinguishes itself from the sibling 'generate_image', so an agent must infer when a logo tool is preferable to a generic image tool.

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?

There is no when-to-use/when-not-to-use guidance and no mention of alternatives such as generate_image or edit_image_with_text. The only directional text is a client-model instruction about extracting the prompt parameter, which is parameter handling rather than tool-selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.