Skip to main content
Glama

Ask about policies

ask_business
Read-onlyIdempotent

Answers delivery, returns, exchange, payment, warranty and care questions from what the business published: its FAQs, its website and, for Shopify stores, the store’s own policies. Says how to reach the team when it has no answer.

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": {
      "business": "<business>",
      "question": "<question>"
    },
    "name": "ask_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessYesThe business id from find_businesses, e.g. "carat-story".
questionYesThe customer’s question, e.g. "Do you deliver to Delhi?"

Output Schema

NameRequiredDescriptionDefault
noteYes
answersYes

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds genuinely new behavior: answers are grounded in published business content (FAQs, website, Shopify policies) rather than generated freely, and there is a defined fallback when no answer exists. It omits any caveat about answer coverage or citation, keeping it from 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.

Conciseness5/5

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

Two sentences, no filler. The core capability and its sources come first, with the fallback behavior trailing as secondary detail — appropriately front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with full schema coverage, rich annotations and an output schema, the description covers what it does, what it reads from, and what happens when it cannot answer. Nothing an agent needs in order to call it correctly is missing.

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 100% and both parameters carry examples, including the note that 'business' comes from find_businesses. The description adds no further parameter meaning, so the schema does the work and the baseline of 3 applies.

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?

States a specific verb ('answers') plus a precisely bounded question domain (delivery, returns, exchange, payment, warranty, care) and names the sources it draws from (FAQs, website, Shopify policies). That scoping clearly separates it from product-lookup siblings like search_products or get_business, so an agent can pick it without opening another schema.

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?

The description gives a clear context of use: customer questions about business policies, answered from published material. It also flags the no-answer path ('says how to reach the team'), which implicitly routes toward a handoff. It stops short of naming an alternative tool or stating exclusions (e.g., order-status questions), so it is clear but not fully routing-aware.

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