Skip to main content
Glama

NewzAI News MCP server

get_user_preferences

Read-only

Returns all saved news preferences for the authenticated user. Each preference contains a news category, region, output language, last_n_hours, search_type, and enable_decay. Login is required to access this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / result / items / properties / region / enum
      Added value: +[
      +  "india",
      +  "united-states",
      +  "united-kingdom",
      +  "japan",
      +  "australia",
      +  "canada",
      +  "germany",
      +  "international"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / result / items / properties / search_type / enum
      Previous value: -[
      -  "vector",
      -  "hybrid",
      -  "sparse",
      -  "exact"
      -]New value: +[
      +  "vector",
      +  "hybrid",
      +  "sparse",
      +  "exact",
      +  "auto"
      +]
  3. Changed6 schema fields changed
    • removedOutput schema / properties / result / items / properties / daily_refresh_time
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / result / items / properties / enable_decay
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / result / items / properties / last_n_hours
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / result / items / properties / search_type
      Added value: +{
      +  "enum": [
      +    "vector",
      +    "hybrid",
      +    "sparse",
      +    "exact"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / items / properties / similarity_threshold
      Added value: +{
      +  "enum": [
      +    "high",
      +    "medium",
      +    "none"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / result / items / required
      Previous value: -[
      -  "id",
      -  "category",
      -  "region",
      -  "language",
      -  "daily_refresh_time"
      -]New value: +[
      +  "id",
      +  "category",
      +  "region",
      +  "language",
      +  "last_n_hours",
      +  "search_type",
      +  "enable_decay",
      +  "similarity_threshold"
      +]
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, so tool is safe read. Description adds that it returns specific fields and requires authentication, going beyond annotations.

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?

Two sentences, front-loaded with main action. Every word earns its place.

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

Completeness5/5

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

Simple tool with no parameters and output schema present. Description covers purpose, returned fields, and authentication. Complete.

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?

No parameters, so schema coverage is 100%. Description needs no further param info; baseline 4 is appropriate.

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?

Description clearly states it returns saved news preferences and lists the fields included. Distinguishes from sibling tools like set_user_preferences and update_user_preferences.

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?

States login requirement, which is a key prerequisite. Does not explicitly describe when not to use, but the purpose is clear and siblings indicate write alternatives.

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