Skip to main content
Glama
Sign In
mcp-google

mcp-google

by Antonio-byte10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remover fontes

notebook_fonte_remover
Destructive

Permanently deletes confirmed sources from a NotebookLM notebook, requiring explicit user approval before removal to prevent accidental deletion.

Instructions

Remove fontes do notebook PERMANENTEMENTE. Só use quando o usuário pedir e confirmar quais.

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>",
      "fontes": "<fontes>",
      "confirmar": "<confirmar>"
    },
    "name": "notebook_fonte_remover"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontesYesTítulos (ou partes) ou ids das fontes.
notebookYesId, URL ou título do notebook (o título pode ser parcial).
confirmarYesPrecisa ser true: confirma que o usuário pediu a remoção.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to add context, which it does by emphasizing permanence and requiring user confirmation. It adds a bit of value on top of the safety profile the annotations already carry, but does not go further into irreversibility or downstream effects.

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?

Two short sentences with zero waste, and the critical constraint (permanence) is front-loaded ahead of the usage rule.

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?

The tool's safety profile is already covered by annotations, and the confirmation sweep is enforced by the schema's confirmar const:true. The description supplies the permanence warning and usage gate, leaving only minor gaps (such as what happens to derived artifacts) for this destructive operation.

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 three parameters (fontes, notebook, confirmar) are already documented in the schema with const/true constraints. The description only implies that confirming which sources matters and adds no syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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 (remove sources from a notebook) plus a strong consequence adverb (PERMANENTEMENTE), which makes the effect unmistakable. It does not explicitly distinguish itself from sibling notebook_excluir or notebook_fonte_renomear, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Só use quando o usuário pedir e confirmar quais" gives a clear precondition for invocation (explicit user request plus confirmation of which sources). It does not name an alternative tool or describe when not to use it versus siblings, so it is not a 5.

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