Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_mark_read

Idempotent

Marks a Bale chat as read using its chat ID, optionally specifying the chat type. Note that this can send read receipts visible to other participants.

Instructions

Mark a chat as read (others may see read receipts).

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": {
      "chat_id": "<chat_id>"
    },
    "name": "bale_mark_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYesChat id from bale_list_chats (user, group or channel id).
chat_typeNoChat type. Optional if the chat appeared in bale_list_chats before.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the description's real contribution is the side-effect disclosure that others may see read receipts — a visible consequence not captured in the annotations. It stops short of saying whether unread counters are cleared or what is returned, but the added behavioral context is meaningful.

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?

A single sentence with the action front-loaded and the caveat in parentheses; every word earns its place with no redundancy.

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?

For a simple two-parameter mutation with full annotation coverage and no output schema, the description covers the action and its user-visible effect adequately. Only the return/confirmation behavior and the chat_type prerequisite nuance are left implicit.

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% and both parameters are documented in-schema, including the enum for chat_type and the provenance of chat_id from bale_list_chats. The description adds no parameter meaning beyond that, so the baseline of 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 states a specific verb and resource ('Mark a chat as read'), making the action unambiguous. It does not, however, differentiate itself from the similarly named sibling bale_read_chat or from bale_get_unread, so an agent must infer the boundary.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of when not to use it. Given the presence of closely related siblings (bale_read_chat, bale_get_unread), a routing sentence would have been valuable and is entirely absent.

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