Skip to main content
Glama

post-describe-style-inferences

Analyzes images or AI models to identify and describe their visual style characteristics for creative applications.

Instructions

Describe the style of the given images or models.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNo
ensureIPClearedNoWhether we try to ensure IP removal for new prompt generation.
imagesNo
seedNoIf specified, the API will make a best effort to produce the same results, such that repeated requests with the same `seed` and parameters should return the same outputs. Must be used along with the same parameters including prompt, model's state, etc..
unwantedSequencesNo
modelIdNoThe modelId used to condition the generation. When provided, the generation will take into account model's training images, examples. In `contextual` mode, the modelId is used to retrieve additional context from the model such as its type and capabilities.
temperatureNoThe sampling temperature to use. Higher values like `0.8` will make the output more random, while lower values like `0.2` will make it more focused and deterministic. We generally recommend altering this or `topP` but not both.
assetIdsNo
topPNoAn alternative to sampling with temperature, called nucleus sampling, where the model considers the results of the tokens with top_p probability mass. So `0.1` means only the tokens comprising the top `10%` probability mass are considered. We generally recommend altering this or `temperature` but not both.
Behavior2/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 of behavioral disclosure. It states the tool 'describes' style, implying a read-only analysis, but doesn't disclose critical traits like whether it modifies data, requires authentication, has rate limits, or what the output format is (e.g., text description, scores). For a tool with 9 parameters and no annotations, this is a significant gap.

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?

The description is a single, efficient sentence with no wasted words, making it appropriately sized. However, it's not front-loaded with critical details (e.g., output type or key parameters), so it's concise but could be more structured for clarity.

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 the tool's complexity (9 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what 'style' entails, how results are returned, or the tool's behavior, leaving significant gaps for an AI agent to understand and use it effectively.

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

Parameters3/5

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

Schema description coverage is 56%, with some parameters like 'seed' and 'temperature' well-documented in the schema. The description adds no meaning beyond the schema, as it doesn't explain how parameters like 'images', 'modelId', or 'unwantedSequences' relate to style description. With moderate schema coverage, the baseline is 3, but the description fails to compensate for the 44% undocumented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Describe the style of the given images or models' states a clear verb ('describe') and resource ('style of images or models'), but it's vague about what 'style' means (e.g., artistic, technical, or other attributes) and doesn't distinguish it from siblings like 'post-caption-inferences' or 'post-detect-inferences', which might also analyze images. It's adequate but lacks specificity.

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 provides no guidance on when to use this tool versus alternatives, such as other inference tools in the sibling list (e.g., 'post-caption-inferences' for general descriptions or 'post-detect-inferences' for object detection). There's no mention of prerequisites, context, or exclusions, leaving usage unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pasie15/scenario.com-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server