Look up a Hepsiburada merchant by slug or store URL to retrieve its ID, name, alias, URL, and product count.
Get a Hepsiburada merchant (store) by slug or store URL: id, name, alias, url and number of products. Flat 5 points per successful run.
| Name | Required | Description | Default |
|---|---|---|---|
| merchant | Yes | Merchant slug or store URL. e.g. efeturk |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It usefully discloses the returned fields and a flat 5-point cost per successful run, but does not cover failure behavior, URL format constraints, or rate-limit/auth considerations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences with the core lookup behavior front-loaded. The returned fields and pricing note are useful and not padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter lookup with full schema coverage and no output schema, the description gives enough context: it names the resource, input forms, returned fields, and cost. It could be more complete with error-case or URL-format notes, but nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the schema already documents the single parameter as a merchant slug or store URL with an example. The description repeats that input form but adds no syntax or validation details beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific verb and resource: "Get a Hepsiburada merchant (store)". It also lists the exact fields returned and distinguishes the singular merchant lookup from siblings like run_hepsiburada_merchants_products.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
States the accepted input forms (slug or store URL), which implies when to use it, but gives no explicit guidance on when to choose it over related tools such as run_hepsiburada_merchants_products or run_hepsiburada_products_sellers.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.