Skip to main content
Glama

MadMax Trade Supply parts

Store policies

get_store_policies
Read-only

Shipping, sales tax, payment, returns, subscriptions and contact details for MadMax Trade Supply.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, self-contained nature of the call is established without the description. The description adds the topical scope of the returned policy set, but says nothing about size, structure, or whether values are store-wide defaults versus conditional rules. Given the annotation coverage, this is adequate but thin.

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?

A single tight sentence with the subject (the store) and the covered topics front-loaded, and no filler. The comma-separated topic list is dense but every item earns its place by telling the agent what the call returns.

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?

For a zero-parameter read with annotations covering the safety profile and no output schema, the description gives enough to decide whether to call it. It does not describe the shape of the response — whether policies come back as structured fields, sections, or prose — so an agent cannot anticipate what it will need to parse or whether to narrow the question first.

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 takes no parameters, so there is no parameter semantics to explain; the baseline for a zero-parameter tool applies. The description correctly implies a single global policy document with no filtering options, which matches 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 names the concrete resource contents — shipping, sales tax, payment, returns, subscriptions, contact — so an agent knows exactly what information this retrieves. It lacks an explicit verb and never contrasts itself with siblings like get_product or create_checkout_link, but the topical enumeration makes the purpose unambiguous in practice.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when a shopper asks about shipping, returns, payment or tax terms. There is no explicit 'use when' statement, no mention of when not to use it, and no routing to alternatives such as get_product for product-specific questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources