SimoShop

Caută produse SimoShop

cauta_produse

Read-onlyIdempotent

Caută în catalogul simoshop.ro după cuvinte cheie în română (1-3 cuvinte, fără diacritice, de exemplu 'banut mot fetita' sau 'bratara nume') sau după codul produsului (de exemplu 'E1830'). Întoarce pentru fiecare produs: cod, denumire, preț în lei cu TVA, disponibilitate, linkul paginii de produs, câmpurile de personalizare (dacă există) și, când e disponibil, linkul de adăugare în coș.

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": {
      "cuvinte": "<cuvinte>"
    },
    "name": "cauta_produse"
  }
}

Input Schema

Name	Required	Description	Default
`limita`	No	Câte produse să întoarcă, între 1 și 10. Implicit 8.
`cuvinte`	Yes	Cuvinte cheie în română, 1-3 cuvinte, fără diacritice (ex. 'banut mot fetita', 'bratara nume'), sau codul produsului (ex. 'E1830').

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

addedInput schema / properties / cuvinte / description

Added value: +"Cuvinte cheie în română, 1-3 cuvinte, fără diacritice (ex. 'banut mot fetita', 'bratara nume'), sau codul produsului (ex. 'E1830')."

addedInput schema / properties / limita / description

Added value: +"Câte produse să întoarcă, între 1 și 10. Implicit 8."

First observedNov 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered. The description adds the shape of the results (code, name, price with VAT, availability, link, personalization fields, add-to-cart link), which is helpful context but overlaps with the existing output schema rather than disclosing new behavior such as ranking or empty-result handling.

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?

Three sentences with zero filler, front-loaded with the action and the source catalog, then the accepted input forms, then the return contents. Every clause carries information an agent can act on.

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?

With a full output schema, complete parameter documentation and rich annotations, the description covers everything needed to invoke the tool correctly. The only gap is the relationship to the sibling top_produse, which would help an agent choose between them.

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% — both 'cuvinte' and 'limita' are documented in the schema, including the 1-10 range and default of 8. The description only restates the keyword/code format with the same examples, adding no meaning beyond the schema, so the baseline 3 applies.

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 ("Caută") and resource ("catalogul simoshop.ro") plus the two accepted query modes (keywords or product code), so the agent knows exactly what the tool does. It never mentions the sibling top_produse, so the differentiation that a 5 requires is absent.

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?

Gives practical query-construction guidance (1-3 Romanian words, no diacritics, or a product code like 'E1830'), which implies when the tool fits. However, there is no explicit statement of when to use this instead of top_produse, and no exclusions or failure conditions.

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

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