Skip to main content
Glama

The Builders Supply catalog

Store policies

store_policies
Read-onlyIdempotent

Shipping, free shipping, freight, returns, refunds, warranty, payment and contact rules of the store in plain text, with links to the full pages.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the agent knows this is a safe, repeatable, closed-world read. The description adds return-shape context ('in plain text, with links to the full pages') that is genuinely useful, but says nothing about coverage limitations, freshness of policy text, or whether some policy categories may be absent for a given store. Adequate, not rich.

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 compact sentence with no filler, and the highest-value information (what policy topics are covered) is front-loaded. The comma-separated topic list is a little list-heavy and the trailing 'with links to the full pages' is somewhat incidental, but nothing is wasted.

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?

With no parameters, a present output schema, and annotations covering the safety profile, the description only needs to convey scope and this it does. An agent has everything required to decide to call it and to interpret what comes back; only the absence of explicit usage routing keeps it from a 5.

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 zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The topic enumeration in the description effectively communicates the scope of what gets returned, which is the only semantic dimension left for a parameterless tool.

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 the concrete policy domains covered (shipping, freight, returns, refunds, warranty, payment, contact) and thereby makes clear this tool returns store policy content rather than product data, distinguishing it from the product-oriented siblings. It lacks an explicit verb such as 'Retrieve', reading as a topic list rather than a statement of action, which keeps it short of 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 Guidelines3/5

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

No explicit when-to-use statement or named alternative appears; guidance is only implied by the enumerated topics, which tell an agent this is the tool for policy questions rather than catalog queries. Since the sibling set (search_products, get_product, browse_category) covers a different domain, the risk of mis-selection is low, but the routing is inferred rather than stated.

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