Skip to main content
Glama

Coline

Password-protect a page

set_page_password
Idempotent

Sets or removes the password on a published note.

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

Input Schema

NameRequiredDescriptionDefault
fileIdYesFile or folder id from list_drive_files, search or fetch.
passwordYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already state readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds that the target must be published and that the operation can both set and remove, but it discloses nothing about permission/auth requirements, what happens if the note is unpublished, or whether existing passwords are overwritten.

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 no filler. It is efficient, though the terseness is arguably what leaves the set-vs-remove mechanics and the page/note wording unresolved.

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?

Output schema exists and annotations cover safety, so the bar is lower. Still, for a 3-required-parameter mutation the description omits permission requirements, the null-password removal convention, and behavior on unpublished content — gaps an agent would need before calling confidently.

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 coverage is 67% — fileId and workspace are documented in-schema, while password (string max 72 or null) has no description. The description's "sets or removes" is the only hint that null removes the password, but it does not state that explicitly, leaving the most consequential parameter convention half-implied.

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?

A specific verb pair plus resource: "Sets or removes the password on a published note." An agent can tell this is a password-mutation tool on published content, distinct from publish_page/unpublish_page/set_file_access. Minor friction: it says "note" while the title and schema (fileId) imply page/file, so the object is slightly ambiguous.

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?

The phrase "on a published note" implies a prerequisite (the note must already be published, cf. publish_page), which is useful. However there is no explicit when-to-use/when-not guidance, no mention that removal is the same call with a null password, and no routing to a sibling such as set_file_access for non-published files.

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