Skip to main content
Glama

Informações da loja

get_store_info
Read-only

O que é a Casa do Artesão e suas políticas: envio e frete grátis, trocas e devoluções, formas de pagamento, horário de atendimento, contatos, endereço da loja física e como comprar pelo assistente. Use antes de responder dúvidas sobre a loja.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the content scope of the response (policies, contacts, address, purchase instructions), which matters because there is no output schema. It stops short of saying whether the information is static or authoritative, so it is good but not rich behavioral context.

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?

Two sentences: the first front-loads the itemized coverage, the second states the routing condition. The enumeration is long but each item signals a distinct topic the agent can rely on, so nothing is filler.

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 zero-parameter, read-only lookup with no output schema, the description carries the burden of describing what comes back, and it does so thoroughly via the topic list. Only a note on freshness/authority of the information is missing.

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, so the baseline is 4; there is nothing for the description to disambiguate. The description correctly implies a no-argument lookup by framing the tool as a fixed body of store information.

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 names the concrete resource (Casa do Artesão) and enumerates exactly what it covers: shipping/free-shipping rules, exchanges and returns, payment methods, service hours, contacts, physical address, and how to buy via the assistant. That is far more specific than a bare title, though it never contrasts itself with any named sibling (the siblings are clearly transactional, so the separation is easy to infer).

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

Usage Guidelines4/5

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

"Use antes de responder dúvidas sobre a loja" gives clear when-to-use guidance tied to store-policy questions. There is no explicit when-not clause or named alternative, but the trigger condition is unambiguous enough for routing.

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