Skip to main content
Glama

MagSnap — Custom Photo Magnets & Gift Printing Store

get_store_faq

Retrieve official MagSnap product specifications, material durability, production turnaround, and courier delivery policies across South Africa.

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_faq"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoSpecific FAQ topic or 'all' for complete store overview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"Specific FAQ topic or 'all' for complete store overview. [Optional: omit to use server default filter]."New value: +"Specific FAQ topic or 'all' for complete store overview."
  2. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"Specific FAQ topic or 'all' for complete store overview."New value: +"Specific FAQ topic or 'all' for complete store overview. [Optional: omit to use server default filter]."
  3. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Retrieve' implies a read, but nothing is said about whether results are static policy text, whether auth is required, how much content is returned, or what happens with the optional topic omitted – all meaningful gaps for an unannotated tool.

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 front-loaded sentence with a clear verb and no filler sentences; every clause describes covered content. Slightly overloaded with qualifiers ('official', 'across South Africa') that add locale bias without much selecting power.

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 optional-parameter read tool with no output schema, the description covers the content scope reasonably. It still leaves ambiguous overlap with get_products and omits two enum topics, so an agent cannot fully predict what a call returns.

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 enum parameter is self-documenting, so the schema already does the work. The description adds a loose mapping between its listed subjects and the enum, but never explains the 'returns' or 'ai_styling' values, which appear in the enum but not in the prose.

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?

States a specific verb ('Retrieve') and enumerates the resource classes (specifications, durability, turnaround, delivery policies), so the agent knows it is a policy/reference lookup. It does not, however, differentiate itself from the sibling get_products, whose 'specifications' overlap with this tool's stated scope.

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 by the listed subject matter – the agent can infer this is for policy-style questions rather than cart or quote actions. There is no explicit when-to-use/when-not guidance and no mention of the alternatives (get_products, calculate_quote) that cover adjacent information.

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