Help by DeltaBreen

set_rating_settings

Switch asking customers for a rating on or off. ask shows one to five stars and an optional line under a closed ticket; mail also sends one fixed email a day after a person closed it, to a customer who confirmed their address, and only works with ask on. Owner or admin; Pro and higher.

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": {
      "ask": "<ask>",
      "mail": "<mail>"
    },
    "name": "set_rating_settings"
  }
}

Input Schema

Name	Required	Description	Default
`ask`	Yes	Ask customers how it went once their ticket is closed: true to switch it on.
`mail`	Yes	Also ask by one email, a day after a person closed the ticket. Needs `ask`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only tell the agent this is a non-read-only, non-destructive write; the description adds real context: effect of each flag (stars plus optional line under a closed ticket; one fixed email a day after a human closes it), the constraint that mail only works with ask on, recipient confirmation requirement, and the auth/plan gate. It stops short of saying what happens to existing ratings when the toggle is switched off, which is the remaining behavioral unknown.

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 clauses, front-loaded with the action, then the modes, then the access constraints. No filler and no repetition of the schema's mechanical type 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?

For a two-boolean settings toggle with no output schema, the description covers purpose, mode interactions, dependencies, permissions, and plan requirements. The only gap is the state of previously collected ratings when switching off, which matters for a settings mutation.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds interaction semantics the schema fields only gesture at: mail depends on ask, is limited to one email per day after close, and only reaches customers with a confirmed address. That dependency pairing is the main thing an agent needs to avoid an invalid combination.

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?

Opens with a specific verb and resource: 'Switch asking customers for a rating on or off.' It is immediately distinguishable from the sibling get_rating_settings (read) and from the other set_* configuration tools, and the two modes it controls are named inline.

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?

The description makes clear this is the write counterpart to the read-side rating settings and states the preconditions (owner or admin role, Pro plan or higher) an agent must satisfy before calling. It does not explicitly name get_rating_settings as the alternative for inspecting current state, so the routing hint is implied rather than stated.

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

All Help by DeltaBreen 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?