Skip to main content
Glama

Coline

Show Drive

show_drive
Read-onlyIdempotent

Shows the person's Drive inside the chat: browse drives and folders, see recent and starred files, preview a file's text. Use it when they want to look through their files.

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>"
    },
    "name": "show_drive"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNorecent and starred span every drive.default
limitNo
cursorNo
driveIdNoDefault: the person's default drive.
parentIdNoA folder; default: the drive's top level.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
filesYes
driveIdYes
folderIdYes
driveNameYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real context by noting it renders "inside the chat" and produces a preview of file text, but says nothing about preview truncation/size limits, pagination of browse results, or what happens when the drive is empty or inaccessible.

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?

A single front-loaded sentence with a colon-delimited capability list; no filler. The only weakness is that the enumerated clause is dense and does not foreground the required workspace scoping.

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?

With six parameters, one required, an output schema present, and only 67% schema description coverage, the description is adequate but thin. It never mentions the required workspace slug or the limit/cursor pagination, so an agent still needs to read the schema for basic invocation correctness.

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

Parameters4/5

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

Schema coverage is 67%, so the schema carries most of the load and baseline would be 3. The description does add meaning that maps to parameters: "recent and starred" cues the view enum and its cross-drive scope, and "browse drives and folders" cues driveId/parentId navigation — modest but genuine value above the schema.

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+resource ("Shows the person's Drive") and enumerates the sub-capabilities: browsing drives/folders, recent and starred views, and file text preview. It is clearly a read/browse surface distinct from mutation siblings like create_shared_drive or trash_drive_file, though it never names the closest sibling list_drive_files to differentiate.

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?

"Use it when they want to look through their files" gives a general usage condition, but there are no exclusions or explicit alternatives — an agent cannot tell from this text whether list_drive_files or show_doc is the better pick for a given request.

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