Skip to main content
Glama
Sign In
viberoom

viberoom

by RatulMaharaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_rating

Rate an image from 0 (unrated) to 5 stars to organize and filter your RAW photo collection.

Instructions

Set the star rating, 0 (unrated) to 5.

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": {
      "image_id": "<image_id>",
      "rating": "<rating>"
    },
    "name": "set_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingYes
image_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only states that the tool sets a rating and the valid range; it does not mention whether the rating overwrites an existing value, requires specific permissions, or how invalid values are handled.

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?

The description is a single clear sentence, front-loaded with the action and scope. Every word contributes meaning and there is no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is thin. It fails to mention how the rating relates to the broader image workflow, what happens on invalid input, or any return/error behavior, leaving significant context unaddressed.

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?

The schema provides no descriptions for the two parameters, and the description compensates by explaining the rating range and the meaning of 0 as unrated. However, it does not clarify the image_id parameter beyond what its name implies, leaving a partial gap.

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?

The description uses the specific verb 'Set' with the resource 'star rating' and defines the range 0-5, making it clear what the tool does. It distinguishes itself from sibling tools like set_flag and set_library by naming the rating concept.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives, such as set_flag or set_recipe. There is no mention of prerequisites, context, or known alternatives, leaving the agent to infer usage from the name alone.

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

Deploy Server

Other Tools