Skip to main content
Glama

My preferences

preferences_get
Read-onlyIdempotent

Your own client-portal preferences exactly as the Preferences page shows them: language (with the active options), theme, calendar, which notifications you get by email or Telegram (categories not live yet are marked), preferred contact channel and whether you agreed to marketing messages. Only the signed-in account. No email address, phone number or ids are returned.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoReserved for the display language. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it scopes results to the signed-in account only and explicitly states that no email address, phone number or ids are returned, which tells the agent what it will not get. It does not, however, explain whether the reserved locale parameter alters the returned language, which is the one behavioral question an agent would still have.

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?

Front-loaded with the resource and its scope, then the field inventory, then the negative guarantees about what is excluded. The field enumeration is dense but each clause carries distinct information; only the parenthetical about notification categories being marked is slightly incidental.

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?

There is no output schema, so the description carries the return-shape burden and discharges it by listing the preference fields and stating what is withheld for privacy. For a zero-required-parameter read tool with full schema coverage, that is close to complete; only the effect of locale is left unresolved.

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 the single optional locale enum is already documented as 'Reserved for the display language. Default en.' The description mentions language only as a returned field ('with the active options') and never clarifies whether passing locale changes the output language or is ignored, so it adds no meaning over the schema. Baseline 3 applies.

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 names a specific resource (the signed-in account's client-portal preferences) and enumerates the fields returned: language, theme, calendar, notification channels, contact channel, marketing consent. That is far more specific than a tautology, though it never explicitly contrasts itself with the sibling preferences_update, so the read-vs-write split is left to the name.

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?

Usage is only implied: 'Your own... Only the signed-in account' makes clear this is a self-scoped read, but there is no statement of when to call it, no prerequisite, and no pointer to preferences_update for changes. Adequate but with a clear gap.

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