Skip to main content
Glama
Sign In

Magento MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Magento Setup Helper

query_contexts
Read-only

Helper for planning InsightfulPipe Magento data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, AND available_actions.

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

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": {
      "request": "<request>"
    },
    "name": "query_contexts"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionsNo
requestYes
brand_idNo
platformNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true; the description adds that this is planning/setup only and explains what each request returns, including workspace_id, brand_id, available_actions, request bodies, identifiers, fields, and time ranges. It does not discuss error or rate-limit behavior, but the important read-only workflow context is present.

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?

The numbered workflow is front-loaded and every bullet serves the setup sequence. Optional notes are useful rather than repetitive, especially the clarification that available_actions is already included in the accounts response.

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 five-parameter setup helper with annotations and an output schema, the description explains the required discovery flow and return contents well. The unexplained platform parameter is the main remaining gap.

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 0%, so the description must carry parameter semantics; it thoroughly explains the request enum values, plus actions and brand_id/workspace_id usage for brands. However, it never explains the platform parameter, leaving a meaningful gap.

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 it is a helper for planning InsightfulPipe Magento data queries and outlines the discovery calls, so the resource and role are clear. It does not name sibling tools or explicitly contrast execution/querying, leaving sibling differentiation implicit rather than explicit.

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

Usage Guidelines4/5

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

Gives a required Step 1 / Step 2 workflow and marks actions_details as REQUIRED before querying, plus optional calls. It lacks an explicit when-not-to-use statement and does not name sibling alternatives.

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

All Magento MCP by InsightfulPipe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources