Skip to main content
Glama

PowerBankPortatil Store

Shipping, returns and warranty

get_store_policies
Read-only

Shipping prices, delivery time, returns, warranty and payment methods of the store (same rules as the checkout).

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
langNoAnswer language (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "es",
      -  "fr",
      -  "de"
      -]New value: +[
      +  "en",
      +  "fr",
      +  "es",
      +  "de",
      +  "it",
      +  "pt",
      +  "nl"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already tell the agent this is a safe, closed-domain read, so the description carries a lower bar. It adds one useful signal — that the returned rules are the same as those applied at checkout — but says nothing about whether the data is static or frequently updated, or whether shipping prices are geography-dependent.

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?

One compact sentence packs the full topic list up front with no filler. The parenthetical about checkout parity is well placed, though the fragment structure (no leading verb) makes it slightly less immediately actionable.

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 single-parameter read tool with safety annotations covered, the description is nearly sufficient. It leaves open whether policies are global or per-store/region and how it relates to quote_shipping for actual shipping cost, which is the most likely agent confusion given the siblings.

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% and the single optional `lang` parameter is fully documented with its enum and 'default en' note, so the schema does the work. The description adds no meaning about language behavior or fallback, which matches the baseline-3 expectation for a well-covered 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 enumerates concrete resources — shipping prices, delivery time, returns, warranty, payment methods — which is specific enough to distinguish it from product- or compatibility-oriented siblings. It lacks an explicit verb (e.g. 'retrieve') and does not differentiate itself from the sibling quote_shipping, so a 4 rather than a 5.

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 statement of when to use this tool, nor any exclusions or pointer to alternatives. An agent must infer that static, store-wide policies belong here while destination-specific shipping prices belong to quote_shipping — an inference the description never confirms.

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