Skip to main content
Glama

Mark conversation read

mark_conversation_read

Marca conversas como lidas (somem do filtro "Não lidas" da tela do dono da chave) ou, com nao_lida=true, volta a marcar como não lidas. Ler mensagens pelo MCP nunca marca sozinho: chame esta ferramenta só quando a pessoa pedir.

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_ids": "<conversation_ids>"
    },
    "name": "mark_conversation_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
nao_lidaNotrue = volta a marcar como não lida. Padrão: marca como lida.
conversation_idsYesIDs das conversas (via get_conversations), até 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false / destructiveHint=false / openWorldHint=false, and the description goes beyond that by disclosing the cross-user side effect (the unread badge disappears on the key owner's screen) and the reversibility of the change via nao_lida=true. It does not say what happens with unknown or already-read conversation IDs, nor what the call returns.

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?

Three short sentences, front-loaded with the primary action and its effect, then the inverse mode, then the calling guardrail. No filler and no repetition of the title.

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 2-parameter, fully documented, non-destructive mutation tool with annotations present, the description covers effect, reversibility, and the trigger condition. Only edge cases (invalid IDs, exceeding 50, response contents) are left unaddressed, which is minor given no output schema is expected.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds meaning the schema does not: it explains the downstream consequence of the read/unread state and frames nao_lida=true as a deliberate reversal rather than a generic boolean. The per-parameter wording still largely mirrors the schema.

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?

States a specific verb+resource ('Marca conversas como lidas') plus the inverse operation via nao_lida=true, and describes the concrete observable effect ('somem do filtro "Não lidas" da tela do dono da chave'). An agent can tell this apart from a read/list tool without opening the schema.

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?

Gives an explicit selection condition: 'Ler mensagens pelo MCP nunca marca sozinho: chame esta ferramenta só quando a pessoa pedir' — a clear when-to-use and an implicit when-not (don't call it as a side effect of reading). It stops just short of naming a sibling alternative or describing the 50-item batch limit as a usage constraint.

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