Skip to main content
Glama

Niche of One Network

Store policies

mall_policy
Read-onlyIdempotent

The store's refund policy, terms or privacy policy, as published.

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

Input Schema

NameRequiredDescriptionDefault
kindNo

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 state that the tool is read-only, idempotent, non-destructive, and not open-world. The description adds that the policy is returned 'as published,' which suggests authoritative published content rather than drafts. It does not describe auth needs, rate limits, or return format, but those are less critical for this simple read-only lookup.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no wasted wording. It identifies the resource and its possible variants efficiently.

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?

For a simple read-only policy lookup with one optional enum parameter and no output schema, the description is largely complete. The main remaining gap is the unspecified default behavior when no 'kind' is provided.

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 description coverage is 0%, and the single 'kind' parameter has no documentation in the schema. The description compensates partially by naming refund policy, terms, and privacy policy, which map to the enum values. It does not explain what happens when 'kind' is omitted, even though the parameter is optional.

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 clearly identifies the resource as the store's refund, terms, or privacy policy. It does not use an explicit retrieval verb, but a reader can tell that the tool returns published policy content. No sibling appears to cover the same policy-retrieval purpose.

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?

The description implies usage by naming the policy types, but it does not explicitly say when to use this tool instead of other store tools. It gives enough context for a straightforward policy lookup but no exclusions or alternatives.

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