Skip to main content
Glama

Coline

Star a file

star_drive_file

Stars a file for the person (it shows in their starred files), or unstars it if it's starred.

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": {
      "workspace": "<workspace>",
      "fileId": "<fileId>"
    },
    "name": "star_drive_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesFile or folder id from list_drive_files, search or fetch.
starredNotrue stars it, false unstars it; leave it out to toggle.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
starredYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description adds meaningful context: starring is scoped 'for the person' (personal, not a shared/global flag) and that an already-starred file is unstarred rather than double-starred. This is consistent with idempotentHint=false, since the omitted-parameter toggle makes repeated calls non-idempotent. It does not discuss permissions or whether the target file's share settings matter, leaving a small gap.

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 compact sentence that front-loads the primary action and its user-visible consequence, with no redundant or filler wording.

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?

With full schema coverage, an output schema, and annotations declaring a non-destructive, non-read-only mutation, the description only needs to convey purpose and scope, which it does. Minor gaps around permissions and toggle defaults are already covered by the schema, so nothing essential is missing.

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%; fileId, workspace, and the starred toggle are all documented in the schema itself, including the 'leave it out to toggle' behavior. The description adds no syntax, defaults, or constraints beyond what the schema already states, so the baseline 3 is appropriate.

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 gives a concrete verb+resource pair ('Stars a file') and immediately explains the visible effect ('it shows in their starred files'), so the agent knows exactly what changes. It does not explicitly contrast with siblings such as tag_file or update_drive_file, but the operation is distinct enough that confusion is unlikely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the reader infers this tool is for the personal 'starred' flag rather than labels or sharing. There is no explicit when-to-use/when-not statement, no mention of prerequisites, and no named alternative for related operations.

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