AkulaCyber

Get AkulaCyber product details

akulacyber_get_product

Read-onlyIdempotent

Return the full details of one AkulaCyber product, with a photo attached as an image and a cart_url that opens the store cart with one piece of it; price and stock are read live on every call. Use it when the user names one product or after akulacyber_search_products; for two or more KVMs side by side use akulacyber_compare_kvms, and for several products or quantities in one cart akulacyber_create_cart_link. Pass product as the slug from search results, the model or part number, or the GTIN; lang sets the language of the texts and of the page URL. An unknown product returns an error listing every valid slug.

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": "<product>"
    },
    "name": "akulacyber_get_product"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the texts and page URLs in the answer: uk (Ukrainian, the default), ru (Russian) or en (English). Use the language the user writes in.	uk
`product`	Yes	One product: a slug from search results (gl-rm1), a model or part number (GL-RM1, GL-ATXPC) or a 13-digit GTIN; case does not matter.

Output Schema

Name	Required	Description	Default
`url`	Yes
`code`	Yes
`gtin`	Yes
`name`	Yes
`slug`	Yes
`facts`	Yes
`image`	Yes
`model`	Yes
`images`	Yes
`on_sale`	Yes
`summary`	Yes
`cart_url`	Yes
`category`	Yes
`price_uah`	Yes
`description`	Yes
`availability`	Yes
`category_name`	Yes
`specifications`	Yes
`compatible_kvms`	Yes
`regular_price_uah`	Yes
`compatible_accessories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / lang / description

Previous value: -"Language of the answer: uk (Ukrainian), ru (Russian) or en (English). Use the language of the user."New value: +"Language of the texts and page URLs in the answer: uk (Ukrainian, the default), ru (Russian) or en (English). Use the language the user writes in."

changedInput schema / properties / product / description

Previous value: -"Product slug (gl-rm1), model or part number (GL-RM1, GL-ATXPC) or GTIN, as returned by search."New value: +"One product: a slug from search results (gl-rm1), a model or part number (GL-RM1, GL-ATXPC) or a 13-digit GTIN; case does not matter."

Changed3 schema fields changedNov 9, 2026

addedOutput schema / properties / cart_url
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / image
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "slug",
-  "name",
-  "model",
-  "code",
-  "gtin",
-  "category",
-  "category_name",
-  "price_uah",
-  "regular_price_uah",
-  "on_sale",
-  "availability",
-  "url",
-  "summary",
-  "description",
-  "specifications",
-  "facts",
-  "compatible_accessories",
-  "compatible_kvms",
-  "images"
-]New value: +[
+  "slug",
+  "name",
+  "model",
+  "code",
+  "gtin",
+  "category",
+  "category_name",
+  "price_uah",
+  "regular_price_uah",
+  "on_sale",
+  "availability",
+  "url",
+  "summary",
+  "description",
+  "specifications",
+  "facts",
+  "compatible_accessories",
+  "compatible_kvms",
+  "images",
+  "image",
+  "cart_url"
+]

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, but the description adds real behavioral context beyond them: price and stock are read live on every call (no caching), the response embeds an image and a cart_url, and an unknown product returns an error enumerating valid slugs. It stops short of stating any auth or rate-limit behavior, but for a read-only lookup the disclosure is substantial.

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?

Front-loaded with the return payload, then routing, then parameter guidance, then the error case — a sensible order with little waste. Slightly dense packing of four distinct concerns into two sentences, and "opens the store cart with one piece of it" is awkward phrasing, but nothing is filler.

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, so return values need not be spelled out, yet the description still flags the image and cart_url fields and the live-price behavior. Combined with the error contract and the sibling routing, an agent has everything needed to call this correctly on the first attempt.

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%, so both parameters are already fully documented in the schema, including the enum and slug/model/GTIN examples. The description mostly restates this ("Pass product as the slug... lang sets the language of the texts and of the page URL"), adding only the minor hint that the slug comes from search results. Baseline 3 is appropriate.

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 and resource ("Return the full details of one AkulaCyber product") and immediately scopes it to a single product, with concrete return contents (photo as image, cart_url). It is clearly separable from akulacyber_search_products and akulacyber_compare_kvms by the "one product" framing.

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 user names one product or after akulacyber_search_products") and explicit routing away for the two adjacent cases: two or more KVMs to akulacyber_compare_kvms, several products or quantities to akulacyber_create_cart_link. When-to-use and when-not-to-use are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AkulaCyber tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?