Skip to main content
Glama
Sign In
mcp-magento-cloud

mcp-magento-cloud

by juan-cinto-infracommerce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_variables

List variables for a Magento Cloud project or environment by providing the project ID and environment name.

Instructions

List variables for a Magento Cloud project or environment

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": {
      "project": "<project>",
      "environment": "<environment>"
    },
    "name": "list_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoThe variable level: 'project' or 'environment'. Lists all if omitted.
projectYesThe Magento Cloud project ID
environmentYesThe environment name, e.g. 'staging', 'production'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided; description is too brief, lacking details on whether it returns all variables, read-only nature, or any constraints beyond listing.

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?

Single sentence with no redundant words; efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While adequate for a simple list operation, missing usage guidelines and behavioral details, especially given no output schema or annotations.

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 coverage is 100% with descriptions for each parameter. Description does not add extra meaning beyond schema, so baseline score of 3 is appropriate.

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?

Description clearly states verb 'list' and resource 'variables' for a Magento Cloud project or environment, differentiating it from sibling tools like list_projects and list_environments.

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 on when to use this tool versus alternatives like list_projects or list_log_types. No context on prerequisites or filtering behavior.

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