Skip to main content
Glama

AIFEC

store_info

Read-only

About the shop itself and its policies: what the shop is and sells in its own words (about), returns (the deadline and the text of the returns page, with its link), shipping and terms pages, accepted payment methods, how the invoice reaches the customer (invoices), contact details and opening hours. Call it for any question about the shop that is not about a product. Say you do not know only when this returns nothing for the topic.

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

Input Schema

NameRequiredDescriptionDefault
topicNoall
session_idNoOnly if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds genuinely new behavior: the returns topic returns the deadline plus the page text and its link, and an empty result is the only signal that warrants 'I don't know'. It does not mention truncation, caching, or auth needs, which keeps it below a 5.

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?

The content list is front-loaded before the usage rules, so an agent can pattern-match on topic early. The first sentence is a dense run-on with nested parentheticals, but nearly every clause carries routing or return-content information.

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 read-only, side-effect-free lookup with no output schema, the description does the important work of stating what each topic returns and how to interpret an empty response. It stops short of describing response structure for the composite 'all' case, which is the remaining meaningful gap.

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 50%: session_id is fully documented in the schema and the topic enum values are self-describing. The description does map the topics to their content (e.g., returns yields deadline, page text, and link), but it never explains the 'all' default or the enum's mutual exclusivity, so it only marginally exceeds what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (the shop itself and its policies) and enumerates exactly what is covered: about, returns, shipping, terms, payment, contact, hours. The sentence 'Call it for any question about the shop that is not about a product' cleanly separates it from the product-oriented siblings such as get_product and search_products.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives an explicit inclusion rule ('any question about the shop that is not about a product'), an implicit exclusion (product questions), and a fallback policy ('Say you do not know only when this returns nothing for the topic'). The only minor gap is that no sibling tool is named as the alternative, but the domain split makes routing unambiguous.

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