Skip to main content
Glama
Sign In

Magento MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Magento Data Query

query_data
Read-only

Query Magento data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

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": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable sequencing context (a mandatory two-step preamble, FINAL step) but says nothing about error behavior, response limits, or what happens if the body diverges from the expected structure. Additive but thin against the lowered bar.

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?

Front-loaded with the workflow position and the prerequisite steps; every sentence serves a purpose. The numbered steps border on verbose for such a short definition, but the density is justified by the opaque body schema.

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?

Given a free-form object parameter and an existing output schema, the description supplies the missing piece a schema cannot: where to obtain the correct body structure. It omits failure modes and how to interpret results, but the output schema covers return values.

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

Parameters2/5

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

Schema coverage is 0% and body is an opaque object with additionalProperties=true, so the description carries the full burden. It does not describe any body fields; it only redirects the agent to fetch structure from query_contexts. That is a helpful workaround, but it is indirect and leaves the parameter itself undocumented.

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?

"Query Magento data" gives a verb and a resource, and the parenthetical positions it as the terminal step of a workflow, which is useful context. However, it never distinguishes this from sibling execute_action or clarifies what class of data/actions are reachable, so the agent cannot tell read-query from write-execute without opening the schema.

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?

The description is unusually explicit about preconditions: it names query_contexts, gives the exact request values ('accounts', 'actions_details'), and mandates calling step 2 before querying. It lacks any when-not/alternative guidance against execute_action, which keeps it below a 5.

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