Skip to main content
Glama

Zoya.bg

preferences

Read/update only language, currency and storefront after explicit memory consent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behaviors: mutations are confined to three fields, and a consent gate precedes them. It stops short of saying whether writing without consent errors out, whether unspecified preferences are preserved, or what a read returns.

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

Conciseness4/5

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

One sentence, front-loaded with the consent precondition preceding the scope, with no filler. It is arguably over-compressed given the read/update duality, but nothing is wasted.

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 tool with a single opaque parameter, no annotations and no output schema, the description leaves key operational facts unstated: how a read is distinguished from a write, what the response looks like, and the failure mode without consent. The consent gate is the one genuinely useful addition.

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 0% and the single "values" parameter is an untyped free-form object, so the schema explains nothing. The description compensates by enumerating the only permitted keys (language, currency, storefront), which meaningfully constrains what goes inside that opaque object, though it never explicitly ties the payload to those keys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb pair ("Read/update") and a tightly bounded resource scope: only language, currency and storefront. That field-level restriction distinguishes it from a generic preferences store, though the combined read/write framing leaves some blur about what a single call actually does.

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?

It supplies one hard precondition – the operation may only occur "after explicit memory consent" – which implicitly gates usage and points toward the consent flow among the siblings. It does not state when an agent should read versus update, nor name the consent tool or what to do if consent is absent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources