Skip to main content
Glama
Sign In
viberoom

viberoom

by RatulMaharaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_flag

Mark an image as 'pick' or 'reject' to review and curate your photo library, or clear the flag when no longer needed.

Instructions

Flag an image as 'pick' or 'reject', or None to unflag.

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>",
      "flag": "<flag>"
    },
    "name": "set_flag"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagYes
image_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does explain the flag values and that None unflags, but it does not mention side effects, permissions, overwriting behavior, or return values. This is adequate for a simple setter but lacks depth.

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 concise sentence that is front-loaded with the action and resource. It avoids unnecessary detail while conveying the key information.

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?

Given the tool's simplicity and the schema's clarity, the description is complete enough for an agent to invoke it correctly. It covers the main behavior (set/unset flag) and parameter semantics. It does not elaborate on consequences or error conditions, but these are not critical for a basic flagging operation.

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?

The schema provides no descriptions for parameters (0% coverage), so the description must compensate. It adds meaning by explaining the flag values and the semantics of None (unflag), which is not obvious from the schema alone. The image_id is self-explanatory, so no further detail is needed.

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 clearly states the tool's purpose: flag an image as 'pick' or 'reject', or unflag with None. It uses a specific verb and resource and distinguishes from sibling tools like set_rating by focusing on flagging specifically.

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?

The description implies when to use the tool—when you want to flag an image—but does not explicitly mention alternatives or exclusions. Sibling tools like set_rating exist, but the description does not state when to prefer set_flag over them, leaving the agent to infer.

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