Conecto

Write a Google Drive file

google_drive_upload

Write a text file (up to 4 MB) into a Drive folder (My Drive when folder_id is left out). If a file with that name exists the new one gets a " (1)" name, unless if_exists is replace (which waits for the owner's approval by default) or fail. $0.001. Costs $0.001 per call; nothing if it fails.

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": {
      "name": "<name>",
      "content": "<content>"
    },
    "name": "google_drive_upload"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`content`	Yes
`mailbox`	No	One of the mailboxes the agent may act as; optional when only one is connected.
`folder_id`	No
`if_exists`	No		rename

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare the non-destructive, non-idempotent write profile, and the description adds real value on top: the 4 MB ceiling, the automatic " (1)" rename on collision, the owner-approval delay for replace, and the per-call charge with no charge on failure. It does not say what the call returns (file id/link), which matters for chaining since there is no output schema.

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 collision/if_exists rule is efficiently front-loaded, but the cost sentence is duplicated: "$0.001. Costs $0.001 per call; nothing if it fails." One of those must go, and the fragment "$0.001." is not a sentence.

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?

For a 5-param write tool with no output schema, the description covers the decisions an agent actually has to make: destination default, overwrite policy, size limit, cost. The only real hole is the return value, which an agent needs in order to link or read the uploaded file next.

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 description coverage is only 20% (mailbox only), so the description must compensate, and it does for the two highest-risk params: folder_id's default to My Drive and if_exists' three-way semantics including the approval wait on replace. name and mailbox constraints are left entirely to 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 concrete verb and resource: write a text file into a Drive folder, with an explicit size ceiling and default destination. That is enough to separate it from google_drive_read and google_drive_search without opening either schema, 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 through parameter behavior (folder_id omitted → My Drive; if_exists chooses rename/replace/fail), but there is no explicit 'use this instead of X' routing against files_upload or m365_files_upload, and no advice to search first before overwriting.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Conecto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?