Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gmail_star

Star Gmail conversations by row index, search query, folder, subject match, or all results to highlight important messages for follow-up.

Instructions

Star conversations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gmail_star"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoAct on EVERY conversation of the query/folder list (Gmail's 'Select all' after loading the whole list; repeated until the list is empty for actions that remove conversations from it). Needs query or folder; no index/indexes/match.
indexNoRow index from gmail.list / gmail.search (0 = first row).
matchNoSelect every row whose subject contains this text (case-insensitive).
queryNoRun this Gmail search first and take the rows from its results.
folderNoOpen this folder/label first and take the rows from it.
indexesNoSeveral row indexes (multi-selection).
max_rowsNoWith match, look at most at this many rows from the top.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the whole burden, and it discloses nothing: not idempotency, not reversibility (gmail_unstar exists), not what happens when no target parameter is supplied despite zero required params, and not whether starring affects only the selected rows or the whole thread.

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

Conciseness2/5

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

Two words are technically waste-free but represent under-specification rather than conciseness. There is no front-loaded context, no scope, and nothing for the agent to anchor on.

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

Completeness1/5

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

A mutation tool with 7 parameters, zero required fields, no annotations and no output schema demands far more than a two-word description. An agent cannot tell from this text what must be supplied to select conversations or what the outcome is.

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 the seven selection parameters (all, index, indexes, match, query, folder, max_rows) are thoroughly documented in the schema itself. The description adds no additional selection semantics, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Star conversations" gives a recognizable verb and resource, so the action is identifiable. But with siblings gmail_unstar, gmail_important and gmail_not_important present, the description makes no attempt to distinguish starring from those closely-related actions.

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?

No statement of when to use this versus gmail_important, gmail_label, or gmail_unstar. Nothing about required selection context, though the schema hints a target must come from gmail.list/gmail.search.

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