Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

drive_sort

Change the sort field and direction of the current Google Drive list; the app remembers the order for each view.

Instructions

Change the sort order of the current list (Drive remembers it per view).

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": "drive_sort"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoSort field as shown by Drive: Name, Date modified, Date modified by me, Date opened by me (Shared with me also offers Date shared; search: Most relevant).Name
reverseNoFalse = the field's natural order (A to Z / New to old), true = the opposite.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that Drive remembers the sort per view, which is real behavioral context, but it doesn't state prerequisites (e.g., a list must be open) or whether the change is reversible.

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 front-loaded sentence with no wasted words. The parenthetical adds useful persistence context without bloating the description.

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

Completeness3/5

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

Adequate for a simple UI-state tool with rich parameter schema and no output schema, but it leaves out prerequisite context and any note about reversibility or what happens if no list is open. The description could do slightly more given there are no annotations.

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 both parameters are well documented in the schema. The description adds no additional meaning about 'by' or 'reverse', so 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?

States a specific verb and resource: 'Change the sort order of the current list.' The scope 'current list' distinguishes it from drive_list or drive_search, though no sibling is named explicitly.

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 implied by 'current list' — it should be used while a list view is active. However, it gives no explicit when-not guidance or alternatives, such as using drive_search to filter rather than sort.

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