Skip to main content
Glama
Sign In
stashcat-api-mcp

stashcat-api-mcp

by dclausen01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_conversation_favorite

Toggle a conversation's favorite status by providing its ID and a boolean flag. Mark or unmark a chat as favorite to manage important conversations.

Instructions

Marks or unmarks a conversation as favorite.

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": {
      "conversation_id": "<conversation_id>",
      "favorite": "<favorite>"
    },
    "name": "set_conversation_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
favoriteYestrue to mark as favorite, false to unmark
conversation_idYesConversation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the core action ('marks or unmarks') but does not mention side effects (e.g., idempotency, authentication requirements, or whether it toggles state). This leaves significant behavioral ambiguity for an agent.

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?

The description is a single, concise sentence that directly conveys the tool's purpose without any redundant or extraneous 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?

Given the simple nature of the tool (two parameters, no output schema) and the absence of annotations, the description is minimally adequate but lacks details that would make it fully self-contained, such as behavior when toggling an already-favorite conversation or any permissions needed.

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 input schema already provides full descriptions for both parameters (favorite and conversation_id) with 100% coverage. The description adds no additional parameter semantics, so it relies on the schema as the baseline.

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 clearly states the action ('marks or unmarks') on a specific resource ('a conversation') with a specific attribute ('as favorite'). It distinguishes from sibling tool set_channel_favorite by explicitly mentioning 'conversation' rather than 'channel'.

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?

The description provides no explicit guidance on when to use this tool versus alternatives, such as set_channel_favorite. However, the naming and sibling context imply the distinction, but the description itself does not state any usage conditions or exclusions.

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