Skip to main content
Glama
Sign In

SimoShop

by ro.simoshop
OverviewDiscussionsAdmin

Cele mai vândute pe temă

top_produse
Read-onlyIdempotent

Întoarce cele mai vândute modele din ultimele 12 luni dintr-o temă a catalogului simoshop.ro. Teme acceptate: mot, botez, fetita, baiat, marturie, baita, cristelnita. Aceleași câmpuri per produs ca la căutare, plus categoria și linkul ei.

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": {
      "tema": "<tema>"
    },
    "name": "top_produse"
  }
}

Input Schema

NameRequiredDescriptionDefault
temaYesTema catalogului, una dintre: mot, botez, fetita, baiat, marturie, baita, cristelnita.
limitaNoCâte produse să întoarcă, între 1 și 10. Implicit 6.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limita / description
      Added value: +"Câte produse să întoarcă, între 1 și 10. Implicit 6."
    • addedInput schema / properties / tema / description
      Added value: +"Tema catalogului, una dintre: mot, botez, fetita, baiat, marturie, baita, cristelnita."
  2. 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 readOnly, idempotent, non-destructive and closed-world behavior, so the description only needs to add context. It does add meaningful traits: the fixed 12-month ranking window and the fact that each product carries category and category link beyond normal search fields. It does not explain how sales are measured or what happens when a theme has no sales, which are minor gaps against the annotation coverage.

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?

Three short sentences, front-loaded with the core behavior before the theme list and the return-shape note. The theme list duplicates the schema's enum, which is wasted words, but nothing else is padded.

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?

This is a simple two-parameter read tool with a full output schema, so the bar is low, and the description covers scope, allowed themes and return shape. Remaining gaps—whether results are ordered by sales and how empty themes behave—are small but real for a 'top' query where ranking order matters.

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 the baseline is 3. The description's theme enumeration merely restates the same whitelist already in the schema, and the 'limita' parameter is never mentioned at all, so no new parameter meaning is contributed.

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?

States a specific verb and resource ('Întoarce cele mai vândute modele') together with a precise scope: the last 12 months, restricted to one catalog theme. The reference to 'Aceleași câmpuri per produs ca la căutare' signals its relationship to the sibling cauta_produse, though it never explicitly says how the two tools differ in intent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the tool for bestseller-per-theme questions, but there is no explicit 'use this when... instead of cauta_produse' statement and no exclusions. The theme whitelist narrows the applicable cases but does not route the agent between tools.

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

All SimoShop toolsInspect
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