Skip to main content
Glama

mark_contact_messages_read

Mark the inbound messages for a contact in the approved business as read.

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": {
      "id": "<id>"
    },
    "name": "mark_contact_messages_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare this is a non-destructive, non-open-world mutation, so the safety profile is covered. The description adds only the "inbound" scope, and leaves key behavioral questions unanswered for a state-changing tool: whether it clears all inbound messages or only unread ones, whether the change is reversible, and what the response contains. It also reads as naturally idempotent while idempotentHint is false, which the description does nothing to explain.

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

Conciseness4/5

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

One sentence, front-loaded with the verb and scope, with no filler. It is efficient, though the vague "approved business" phrase spends words without conveying usable meaning.

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

Completeness2/5

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

For a mutation tool with no output schema and a completely undocumented parameter, the definition should at minimum identify what the id refers to, what subset of messages is affected, and what the caller gets back. None of that is present, leaving the agent to guess before performing a write.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter, so the description must carry the load. Saying "for a contact" weakly implies the id is a contact identifier, but the parameter is named only "id" and could plausibly be a message id, so the ambiguity is unresolved and no format or constraint hints are added.

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 pairs a specific verb ("Mark ... as read") with a specific resource ("inbound messages for a contact"), which is enough to distinguish it from siblings like add_contact_note or set_contact_archived. The odd qualifier "in the approved business" is undefined and adds ambiguity rather than precision, and the description never clarifies whether it targets all inbound messages or only unread ones.

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 when-to-use guidance, no stated preconditions (e.g. required permissions, contact must exist), and no routing to alternatives. An agent gets no help deciding between this and related contact tools such as get_contact_history or triage_contact_enquiry.

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