Skip to main content
Glama

Storewire Lite demo store

Get store information

get_store_info
Read-onlyIdempotent

The public facts of Trailhead Supply as its website shows them: company name, address, opening hours, email and phones; every branch with its address, phone, hours, map link and whether orders can be collected there; messenger contact links; accepted payment methods and whether prices include VAT; the store warranty; the return terms; links to the legal pages; and the frequently asked questions with their answers.

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

Input Schema

NameRequiredDescriptionDefault
localeNoAnswer language: en (default en). Names, labels and URLs follow it.

Output Schema

NameRequiredDescriptionDefault
faqYes
storeYes
paymentYes
returnsYes
branchesYes
policiesYes
warrantyYesThe store default warranty; a product may carry its own.
truncatedNoPresent and true only when the answer outgrew the size budget and its last list items were left out; ask narrower to see them.
messengersYes
answer_typeNoWhat this answer is, for rendering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that these are public, website-published facts (i.e., not account- or cart-specific data), but says nothing about freshness/caching, auth requirements, or whether it is the sole source for store facts.

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

Conciseness2/5

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

It is one long semicolon-delimited catalogue of return fields, which largely duplicates what the existing output schema already specifies. The opening clause is front-loaded and clear, but most of the length is spent restating payload contents rather than stating purpose or usage.

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-required-parameter read-only tool with a full output schema, the description is adequate but misallocated: it explains return values (already covered) instead of routing guidance. The only real gap is disambiguation from get_delivery_options on collection/pickup questions.

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 locale parameter is already fully described in the schema, including its enum and the note that names, labels and URLs follow it. The description text does not mention locale at all, so it adds no meaning beyond the schema; baseline 3 applies.

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 resource and framing: 'The public facts of Trailhead Supply as its website shows them', so an agent knows this is the static store-facts lookup. It does not distinguish itself from siblings, notably get_delivery_options, even though 'whether orders can be collected there' clearly overlaps that tool's territory.

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?

There is no explicit when-to-use sentence and no named alternative, but the enumerated topics (hours, branches, payment methods, warranty, returns, FAQ) implicitly signal which question types this tool answers. The overlap with get_delivery_options around collection/shipping is left for the agent to guess.

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.