Skip to main content
Glama

Vitrine: Trending Fashion, Luxury, Sneakers & Design

Rate an answer

rate_results
Idempotent

Tell Vitrine how an answer worked for your shopper, after you have used it. Pass the query_id of a search, trending, find_similar, complete_the_look or shop_the_look answer you received in the last 7 days, a rating ('useful' or 'not_useful'), and optionally liked_ids and disliked_ids (ids from that answer) and a one-sentence comment on what was missing. Liked pieces rise in trend scores for every agent; disliked ones fall. You can only rate answers sent to you; rating the same answer again replaces your rating. Never include personal data. Returns {query_id, rating, liked, disliked, comment_saved, message}.

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": {
      "query_id": "<query_id>",
      "rating": "<rating>"
    },
    "name": "rate_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo
ratingYesDid the results help your shopper? 'useful' or 'not_useful'.
commentNoOptional: what was missing or wrong, in a sentence. No personal data.
query_idYesThe query_id of a search, trending, find_similar, complete_the_look or shop_the_look answer you received in the last 7 days.
liked_idsNoIds from that answer that fit well (optional).
disliked_idsNoIds from that answer that did not fit (optional).

Output Schema

NameRequiredDescriptionDefault
likedNo
ratingYes
messageYes
dislikedNo
query_idYes
comment_savedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare idempotent=true and non-destructive, and the description is consistent with both by explaining that rating again replaces the prior rating. It adds real context the annotations don't carry: likes raise trend scores for every agent, dislikes lower them, and personal data must never be included. The effect on shared/global ranking is disclosed, though the magnitude or timing of that effect isn't.

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?

A single dense paragraph that is front-loaded with the action and eligibility, then effects, constraints, and return shape. Every sentence carries information, though the final return-shape sentence is somewhat redundant given the output schema.

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?

For a mutation tool it covers eligibility, replacement semantics, downstream ranking effects, privacy constraint, and even the return fields, so an agent knows both whether to call it and what to expect after calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 83% schema coverage the schema does most of the work, but the description adds meaning beyond it: query_id must come from a specific eligible answer type within 7 days, liked/disliked ids must be ids from that answer, and comment should be one sentence without personal data. The optional agent object is not explained in the description, but the schema documents it.

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 ('rate an answer' / 'tell Vitrine how an answer worked') and pins down which answer types are eligible (search, trending, find_similar, complete_the_look, shop_the_look), which clearly separates it from the retrieval siblings.

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 preconditions: rate only after using the answer, only answers received in the last 7 days, only answers sent to you. It also states the re-rating behavior (replaces your rating) and that liked/disliked ids must come from that answer, leaving little to infer.

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