Skip to main content
Glama
Sign In

Acrium

by com.acriumautomated
OverviewDiscussionsAdmin

List Shopify price rules

shopify_list_price_rules
Read-onlyIdempotent

The store's price rules: what each discount takes off.

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

Input Schema

NameRequiredDescriptionDefault
project_idNoWorkspace to work in (from list_projects). Leave out for the default one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds only a semantic gloss on what a price rule is; it says nothing about pagination, result volume, or how live Shopify store data is fetched (relevant given openWorldHint).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, which is structurally clean, but the terseness crosses into under-specification rather than efficient front-loading. The one clause present defines the resource instead of stating the action.

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?

No output schema exists, so the description is the only place an agent could learn the result shape, and it says nothing about it. Combined with missing differentiation from shopify_list_discounts, the definition is not complete enough for reliable tool selection even for a simple read-only list tool.

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?

Only one optional parameter exists (project_id) and its schema description coverage is 100%, explicitly covering the default-workspace behavior. The description adds nothing about it, but the baseline of 3 applies when the schema already does the work.

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

Purpose2/5

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

The description is a noun phrase that essentially restates the title ('List Shopify price rules' -> 'The store's price rules'), dropping the list verb entirely. 'What each discount takes off' adds a definition of the resource, but an agent still gets no confirmation of what operation is performed or how this differs from the closely related shopify_list_discounts sibling.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The sibling list contains shopify_list_discounts, which an agent could easily confuse with this tool, and the description offers nothing to disambiguate the two.

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

All Acrium 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