Skip to main content
Glama

Babelii-Diofis Account

Cari di marketplace

search_marketplace
Read-onlyIdempotent

Browse the Babelii Marketplace, where other vendors sell hotspot vouchers, food, services and goods (the same listings as the /marketplace page). Use it when the buyer asks what the marketplace has or names a vendor or a kind of item (for example "makanan", "voucher hotspot", "jasa"); an empty query lists a sample. Read only: stocked hotspot vouchers are ordered like any product (search_products then prepare_purchase), every other listing is bought on its buy_url page, so give the buyer that link. Rows with sold_out=true are real vendor products whose stock is empty right now. The result also carries buy_requests: open requests where buyers say what they are LOOKING FOR (title, kind, quantity, budget, link; never buyer names or contacts). "Barang yang sedang dicari" means buy_requests, not the vendor listings. Each listing has order_via, which says how to buy it: 'search_products ...' means a stocked voucher you can order through search_products (search its title) then prepare_purchase, or the buyer can use buy_url; 'buy_url ...' means only the buy_url page (give the link, do not try prepare_purchase). buy_requests are buyers' wishes that vendors can answer at buy_requests_url, NOT things for sale, so never offer to buy one.

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": "search_marketplace"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
queryNo
vendorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description goes well beyond that by explaining buy_requests semantics and warning "never offer to buy one," decoding sold_out=true, and clarifying that buy_requests carry no buyer names or contacts. It also pre-empts a likely failure mode by instructing the agent not to attempt prepare_purchase on buy_url-only listings.

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?

The routing rules are front-loaded and every block carries operational weight, but the purchase-path logic is restated in the final paragraph after already appearing in the middle, costing some redundancy. Dense and purposeful overall, if near the upper bound of useful length.

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?

An output schema exists, yet the description still explains the non-obvious return semantics (buy_requests vs listings, sold_out, order_via) that an agent would otherwise misread. For a read-only discovery tool with four optional params, nothing needed to call or interpret it 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 0%, so the description must carry parameter meaning, and it only partially does: it explains that an empty query returns a sample and that vendor and item kind can drive the search, but limit is never mentioned and no parameter is named directly. Given four undocumented parameters, this compensates for roughly half the gap.

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?

Opens with a specific verb and resource ("Browse the Babelii Marketplace") and delimits scope precisely: "where other vendors sell hotspot vouchers, food, services and goods (the same listings as the /marketplace page)." This separates it cleanly from search_products, which the description later positions as the ordering path for stocked vouchers.

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?

Gives explicit triggers ("when the buyer asks what the marketplace has or names a vendor or a kind of item") and a concrete disambiguation rule: "Barang yang sedang dicari" maps to buy_requests, not listings. It also names the down-stream alternative for each listing type — search_products then prepare_purchase for stocked vouchers, buy_url otherwise — and states the empty-query behavior ("lists a sample").

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