Skip to main content
Glama

search_policies

Read-onlyIdempotent

Searches store policies for exchanges, returns, shipping, deadlines, warranty, payment, and support to answer customer questions with cited sources.

Instructions

Busca nas políticas da loja: trocas, devoluções, frete, prazos, garantia, pagamento e atendimento.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "search_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds only the topical scope of what can be searched; it says nothing about language expectations, result granularity, or whether an empty answer is possible, and an output schema exists so return shape is not required here.

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?

A single front-loaded sentence with the verb first and the topic enumeration after; no filler or redundancy. The topic list is long but each term narrows the searchable scope, so it earns its space.

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?

The tool is simple, annotations cover safety, and an output schema removes the need to describe returns. What remains missing is guidance on how to phrase the "question" and what to do when the answer is out of scope — modest but real gaps for a retrieval tool.

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% for the single required "question" parameter, so the description must compensate. It partially does by listing the policy domains that can be asked about, but never states that "question" is a free-text natural-language query (presumably in Portuguese), nor any length/format expectation.

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 ("Busca") and resource ("políticas da loja") and enumerates the covered domains — trocas, devoluções, frete, prazos, garantia, pagamento, atendimento. This makes the tool unmistakable against the sibling set (orders, customers, SQL, sales), though it never explicitly names a sibling to contrast with.

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 topic list: an agent can infer it should call this for store-policy questions. There is no explicit when-to-use statement, no when-not, and no mention of an alternative path (e.g. run_sql) for policy data, so routing relies on inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.