Skip to main content
Glama

rate_style

Idempotent

Saves a person’s 1–5 star rating and comment for one of their own styles after a build or fix, using only details they provide and keeping it on the local computer.

Instructions

Save the person's rating of one of their own styles (1 to 5 stars and a comment), as Dinoctor asks after a build or fix. Only rate with what the person told you; never make up a rating. It stays on this computer. Returns { rated, stars }.

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": {
      "id": "<id>",
      "stars": "<stars>"
    },
    "name": "rate_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe person's own style id from my_styles (built-in styles can't be used here).
starsYesThe person's stars, 1 to 5.
commentNoThe person's own words about it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / comment / description
      Added value: +"The person's own words about it."
    • addedInput schema / properties / id / description
      Added value: +"The person's own style id from my_styles (built-in styles can't be used here)."
    • addedInput schema / properties / stars / description
      Added value: +"The person's stars, 1 to 5."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=false, so the description's job is lighter. It adds genuinely new facts: the rating is persisted locally ('stays on this computer'), the return shape is '{ rated, stars }', and ratings must be grounded in what the person said. It does not say whether an existing rating is overwritten or what a failure looks like, leaving a small gap.

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 short sentences, front-loaded with the action and payload, then the sourcing rule, then the persistence/return note. No filler or redundant restatement of the name.

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?

For a simple three-parameter write with no output schema, the description covers the trigger, the data-sourcing rule, local persistence, and the return shape. The only omission is overwrite/error behavior on an existing or invalid rating.

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 all three parameters are already documented, making 3 the baseline. The description adds only a loose framing of stars and comment, and even implies the comment is part of the rating while the schema marks it optional.

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 names a specific verb and resource ('Save the person's rating of one of their own styles'), states the payload (1–5 stars plus a comment), and scopes it to the person's own styles, which separates it from deletion/creation siblings such as delete_style or make_style.

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

Usage Guidelines4/5

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

It gives a concrete trigger ('as Dinoctor asks after a build or fix') and a hard constraint on sourcing the rating ('only rate with what the person told you; never make up a rating'). It does not explicitly name which sibling to use instead for creating or editing styles, so it stops short of full when/when-not routing.

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