Skip to main content
Glama

Babelii-Diofis Account

Tanya Abel (penasihat produk)

ask_abel
Read-onlyIdempotent

Consult Abel (AI Assistant Babelii), Babelii's business adviser, for unclear needs or product selection. Bounded model use; returns catalog recommendations, never places an order. Use direct search when filters are known.

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": {
      "message": "<message>"
    },
    "name": "ask_abel"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: it is a bounded model invocation that returns catalog recommendations and "never places an order" — a meaningful safety boundary for an LLM-backed tool. It does not discuss latency, rate limits, or how open-ended the model's answers can be.

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?

Three short clauses, front-loaded with the purpose, followed by the behavioral constraint and the routing rule. No filler or repeated information from the title.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, the one free-text parameter is the entire interface and its expected content is unaddressed, leaving an agent unsure how to compose the prompt or how specific to be.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, "message", at 0% schema description coverage, and the description says nothing about what it should contain — no hint that needs, budget, category, or context can be encoded there. For a free-text prompt driving a language model, this is the single most important gap and the description does not compensate for it.

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?

Names a specific verb and resource: "Consult Abel (AI Assistant Babelii), Babelii's business adviser." It also scopes the intent ("for unclear needs or product selection") and contrasts with the search tools, so an agent can separate it from search_products/search_marketplace, though the alternative is described generically as "direct search" rather than by name.

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?

Gives both a use condition ("unclear needs or product selection") and a routing rule away from the tool ("Use direct search when filters are known"). What it lacks is an explicit exclusion for adjacent transactional siblings like prepare_purchase or execute_purchase.

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