adobe-firefly-mcp

Overview Schema Source Related Servers Discussions Admin

Adobe Firefly Environment Validator

firefly_validate_environment

Checks authentication, browser health, storage, and credits to ensure Adobe Firefly environment is ready. Returns a readiness score from 0 to 100.

Instructions

Validate the Adobe Firefly environment readiness. Checks authentication, selectors, browser health, cookies, storage, credits, and automation indicators. Returns a readiness score from 0-100.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Jul 22, 2026

removedInput schema / properties / url

Removed value: -{
-  "description": "Optional URL to navigate to before validation. Defaults to current page.",
-  "type": "string"
-}

First observedv0.1.0Jul 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries full responsibility. It implies a read-only diagnostic operation by listing checks (authentication, browser health, etc.) and a readiness score, but does not explicitly confirm non-destructiveness, permissions, or potential side effects.

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 sentences with front-loaded purpose; every sentence provides essential information without redundancy or fluff.

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?

The description adequately covers the tool's function and output for a simple validation tool with no parameters. However, given the similar sibling 'firefly_verify_environment', more distinguishing context would improve completeness.

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?

The tool has zero parameters, so the schema coverage is 100%. The description adds value by detailing what aspects of the environment are validated (authentication, selectors, etc.), which goes beyond the empty schema.

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 clearly states the action ('Validate') and the resource ('Adobe Firefly environment readiness'), and lists specific checks. However, the presence of a sibling tool 'firefly_verify_environment' with a similar name creates ambiguity; the description does not distinguish between validate and verify.

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?

No guidance is provided on when to use this tool versus alternatives like 'firefly_verify_environment' or other siblings. No exclusions or context for appropriate use are mentioned.

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

Deploy Server