Skip to main content
Glama
Sign In
Docs Bridge

Docs Bridge

by dylansantwani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

slides_open

Open a Google Slides presentation in a new foreground Chrome tab, optionally at a chosen slide, so users can view it directly.

Instructions

Open a presentation (optionally at a slide) in a new foreground Chrome tab for the user to see.

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": {
      "deck": "<deck>"
    },
    "name": "slides_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYesGoogle Slides URL or presentation id.
slideNo
accountNoWhich signed-in Google account to use: an index as in /u/N/ URLs (0 = first account) or an email address. Omit for the browser default. Use this for presentations owned by a second (e.g. school) account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.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 the side effect that a new foreground tab is created (focus-stealing), but says nothing about auth requirements, error behavior, or what happens if the deck is not found.

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 zero filler; the verb, resource, side effect, and optional qualifier are all packed in without waste.

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?

No output schema exists, so the description should indicate what is returned (e.g., URL or tab reference) and note the account-selection behavior; it does neither. Adequate for the core action but leaves real gaps for a 3-parameter tool.

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%: deck and account are documented, but slide has no description beyond a minimum of 1. The description only mentions 'optionally at a slide', adding little beyond the schema and leaving indexing semantics (1-based) unexplained.

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 (open) and resource (presentation) plus the concrete effect: a new foreground Chrome tab. It is clearly distinguishable from siblings like slides_read or slides_list, though it does not explicitly name an alternative.

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 'for the user to see' implies the use case is user-facing visual display, but the description never says when to prefer this over slides_read or slides_export. No exclusions, prerequisites, or sibling routing are given.

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