Skip to main content
Glama
Sign In

GoodBarber

by dev.goodbarber
OverviewDiscussionsAdmin

Update loyalty

shop_update_loyalty
DestructiveIdempotent

Update the loyalty points details of a user. Guidance: Update the loyalty points details of a user. | context: user_id, points_count

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": {
      "user_id": "<user_id>",
      "points_count": "<points_count>"
    },
    "name": "shop_update_loyalty"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUnique ID of the user.
points_countYesAmount of loyalty points the user has accumulated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already convey that the operation is mutating, destructive, and idempotent. The description adds no further behavioral details about overwrite semantics, validation, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description repeats the same phrase twice and includes an unexplained 'Guidance:' and '| context' fragment, adding noise without providing useful information.

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

Completeness3/5

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

Basic callable context is present: the resource and required parameters are identified. However, details about the update effect, return behavior, prerequisites, and usage scenarios are missing.

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 covers both parameters with basic descriptions. No additional semantics are provided, such as whether points_count replaces the total or represents an incremental change, or what units/format are expected.

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?

Clearly specifies an update action on a user's loyalty points, with user_id and points_count in the schema. The update verb distinguishes it from read-only tools like shop_get_loyalty.

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 on when to use this tool instead of alternatives such as shop_get_loyalty. It does not clarify conditions for updating, whether points_count is an absolute value or delta, or any prerequisites.

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

All GoodBarber toolsInspect
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