Skip to main content
Glama
Sign In
mcp-google

mcp-google

by Antonio-byte10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Configurar o chat do notebook

notebook_configurar_chat

Configure how a notebook's chat responds by setting its objective—default, learning guide, or custom instructions—and response length.

Instructions

Define como o chat do notebook responde: objetivo (padrão, guia de aprendizado ou personalizado com instruções próprias, até 10.000 caracteres) e tamanho das respostas.

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": {
      "notebook": "<notebook>"
    },
    "name": "notebook_configurar_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
tamanhoNopadrao (Padrão), longa (Mais longa), curta (Mais curta)
notebookYesId, URL ou título do notebook (o título pode ser parcial).
objetivoNopadrao (Padrão), guia_aprendizado (Guia de aprendizado), personalizado (Personalizado)
instrucoesNoPapel, estilo ou objetivo (ex.: 'responda como professor de biologia do ensino médio'). Liga o modo personalizado.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is covered. The description reinforces the configuration nature and the 10,000-character limit, but adds nothing about whether this is a full overwrite of existing chat settings, what happens to the notebook's current configuration, or what is returned on success.

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 dense sentence that front-loads the outcome ('define como o chat responde') and then enumerates the two configurable dimensions. Nothing is wasted, though the parenthetical makes it slightly dense to parse.

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 annotations covering the mutation profile and a fully described schema, the definition is workable. Still missing for a mutation tool: whether changes replace existing settings, whether partial updates are allowed, and the absence of any output schema or mention of the response shape.

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 description coverage is 100%, so all four parameters (including the notebook identifier and the enum meanings) are already documented in the schema. The description restates the objetivo modes and the instruction length cap but adds no semantics beyond the structured fields, so baseline 3 applies.

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 and resource: it defines how the notebook chat responds, naming the two configurable axes (objetivo and tamanho das respostas) plus the 10,000-character cap for custom instructions. An agent can distinguish this configuration tool from conversational siblings like notebook_perguntar or notebook_conversa, 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 only implied — an agent infers this is the tool for tuning chat behavior rather than asking questions. There is no explicit when-to-use/when-not, no mention of prerequisites (e.g., the notebook must exist), and no note about whether configuring replaces prior settings.

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