Prubex

Flag or star a message

mail_flag

Idempotent

Flags (stars) a message, or clears the flag with flagged: false. Use it to mark mail that needs follow-up. Example: { "message_id": "msg_…" }.

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": {
      "message_id": "<message_id>"
    },
    "name": "mail_flag"
  }
}

Input Schema

Name	Required	Description	Default
`flagged`	No	true = flag, false = clear.
`message_id`	Yes	A message id (`msg_…`) from a list or search.

Output Schema

Name	Required	Description	Default
`is_flagged`	Yes
`message_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare that this is a non-read-only, idempotent, non-destructive mutation, so the safety profile is covered. The description adds the follow-up use case and the `flagged: false` clearing behavior, but does not add deeper behavioral context such as permissions, side effects, or return behavior.

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 short, front-loaded, and efficiently structured: action, clearing behavior, use case, and example. Every sentence contributes useful information without waste.

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

Completeness5/5

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

For a simple two-parameter idempotent flag toggle with full schema coverage, rich annotations, and an output schema, the description provides everything needed to call it correctly. No material gaps remain for this tool's complexity.

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%, so both parameters are already well documented in the schema. The description reinforces the `flagged: false` clearing behavior and includes an example, but adds little beyond the schema's own parameter meanings.

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 names a specific verb and resource: flag/star a message, and explicitly covers clearing the flag with `flagged: false`. This is clearly distinct from sibling tools such as `mail_mark_read`, `mail_archive`, and `mail_move`.

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?

It gives clear usage context: 'Use it to mark mail that needs follow-up.' However, it does not name alternatives or state when not to use this tool versus related tools like `mail_mark_read` or `mail_archive`.

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

All Prubex tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?