Skip to main content
Glama

Babelii-Diofis Account

Cek tagihan atau tujuan

inquire_purchase

For products with needs_inquiry (bills, e-wallet top-ups): look up the customer name and amount the buyer must confirm. Rate-limited like the web form and may cost the platform an upstream lookup, so call it once per request and only after the buyer gave the destination. Returns an inquiry_id for prepare_purchase; the lookup result is stored server-side, never trust or resend raw data.

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": {
      "product_ref": "<product_ref>",
      "destination": "<destination>"
    },
    "name": "inquire_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNo
destinationYes
product_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing rate limiting comparable to the web form, potential upstream lookup cost to the platform, the once-per-request constraint, and that the result is persisted server-side and must not be trusted or resent by the agent. These details explain the otherwise surprising readOnlyHint=false/idempotentHint=false combination without contradicting it, since the call creates server-side state and an inquiry_id.

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 dense sentences with the gating condition ('For products with needs_inquiry') front-loaded, followed by operational constraints and the output contract. Every clause contributes information an agent needs; nothing is padding.

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?

Because an output schema exists, the brief note that it returns an inquiry_id is sufficient for return-value understanding. Behavioral caveats (cost, rate limit, server-side storage) are covered, with the only meaningful omission being guidance on the optional amount parameter.

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%, so the description must carry parameter meaning. It effectively explains product_ref (must be a needs_inquiry product) and destination (comes from the buyer before calling), but the optional, nullable 'amount' parameter is never mentioned, leaving its purpose and when to supply it ambiguous.

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 a concrete action ('look up the customer name and amount the buyer must confirm') and scopes it to products with needs_inquiry such as bills and e-wallet top-ups. It also signals the handoff to prepare_purchase via inquiry_id, which separates it from the purchase-execution siblings, though it never explicitly states the negative case (it does not itself complete a purchase).

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?

Provides an explicit precondition chain: only for needs_inquiry products, only after the buyer supplied the destination, and only once per request. It also names the downstream tool that consumes the result (prepare_purchase), so an agent knows both when to call and what to do next.

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