Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

drive.apps.get

Retrieve a specific Google Drive app by its app ID. Returns the app resource as JSON for inspecting app details via the Drive API.

Instructions

Gets a specific app. For more information, see Return user info [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: list.

Input Schema

NameRequiredDescriptionDefault
appIdYes[URL path segment] The ID of the app.
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

NameRequiredDescriptionDefault
idNo
kindNo
nameNo
iconsNo
createUrlNo
installedNo
productIdNo
authorizedNo
objectTypeNo
productUrlNo
useByDefaultNo
supportsCreateNo
supportsImportNo
longDescriptionNo
openUrlTemplateNo
primaryMimeTypesNo
shortDescriptionNo
hasDriveWideScopeNo
supportsMultiOpenNo
secondaryMimeTypesNo
primaryFileExtensionsNo
supportsOfflineCreateNo
createInFolderTemplateNo
secondaryFileExtensionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / appId / description
      Previous value: -"The ID of the app."New value: +"[URL path segment] The ID of the app."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "authorized": {
+      "type": "boolean"
+    },
+    "createInFolderTemplate": {
+      "type": "string"
+    },
+    "createUrl": {
+      "type": "string"
+    },
+    "hasDriveWideScope": {
+      "type": "boolean"
+    },
+    "icons": {
+      "items": {
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "iconUrl": {
+            "type": "string"
+          },
+          "size": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "installed": {
+      "type": "boolean"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "longDescription": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "objectType": {
+      "type": "string"
+    },
+    "openUrlTemplate": {
+      "type": "string"
+    },
+    "primaryFileExtensions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "primaryMimeTypes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "productId": {
+      "type": "string"
+    },
+    "productUrl": {
+      "type": "string"
+    },
+    "secondaryFileExtensions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "secondaryMimeTypes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "shortDescription": {
+      "type": "string"
+    },
+    "supportsCreate": {
+      "type": "boolean"
+    },
+    "supportsImport": {
+      "type": "boolean"
+    },
+    "supportsMultiOpen": {
+      "type": "boolean"
+    },
+    "supportsOfflineCreate": {
+      "type": "boolean"
+    },
+    "useByDefault": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the operation is an HTTP GET returning JSON and describes request-body construction mechanics, but omits auth/permission requirements or error behavior. For a read tool the '[HTTP GET]' hint partially signals safety.

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

Conciseness3/5

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

The core purpose is front-loaded, but the sentence is cluttered with an irrelevant documentation link, an '[HTTP GET]' tag, and body-building mechanics that don't apply to a read. Some content doesn't earn its place.

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?

An output schema exists, so return values needn't be explained, and the required appId is documented. However, for a resource-get tool the description says nothing about access/scoping requirements, leaving a gap an agent would want.

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 100%, so baseline is 3, but the description adds precedence semantics not in the schema ('typed flags win over the params map') and the body_file behavior, which genuinely supplements the parameter definitions.

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 ('Gets a specific app') and distinguishes it from the enumerated sibling ('Siblings over the same resource: list'). Clear enough to select against drive.apps.list, though it doesn't explain what an 'app' is in this context.

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?

Implies when to use by pointing at the 'list' sibling over the same resource, but never states explicit when/when-not conditions or other alternatives. Usage is left to inference.

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