Skip to main content
Glama
Sign In
open-webui-mcp

open-webui-mcp

by TETRA-2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_user_pinned_chats_api_v1_chats_pinned_get

Retrieve the list of chats pinned by the authenticated user.

Instructions

Get User Pinned Chats

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": "get_user_pinned_chats_api_v1_chats_pinned_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.5/5.0
Behavior2/5

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

Since no annotations are provided, the description carries the full burden for behavioral disclosure. It only states 'Get User Pinned Chats' with no details about authentication, rate limits, or what 'pinned' means. The output schema may help, but the description adds minimal behavioral context.

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

Conciseness3/5

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

The description is very short (4 words) and front-loaded, but it lacks any structural detail or additional context. While concise, it is under-specified for a tool that could benefit from a brief note on scope or behavior.

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?

Given the output schema exists, the description does not need to explain return values. However, it does not clarify what 'pinned chats' entails or how this tool differs from other chat retrieval functions. It is adequate but not thorough.

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?

The input schema has zero parameters with 100% coverage, so the description does not need to add parameter meaning. Baseline for 0 parameters is 4, and the description is adequate for this simple case.

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?

The description 'Get User Pinned Chats' clearly states the action (Get) and the resource (User Pinned Chats). It effectively distinguishes from sibling tools like get_session_user_chat_list, get_user_chats, etc., which target different scopes.

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?

No explicit usage guidance is provided. The name implies it is for retrieving pinned chats, but there is no when-to-use or when-not-to-use advice compared to other chat-related tools, leaving the agent to infer context.

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

Deploy Server

Other Tools