Skip to main content
Glama
Sign In
mcp-google

mcp-google

by Antonio-byte10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Renomear fonte

notebook_fonte_renomear

Renames a source within a notebook by specifying the notebook, current source title or ID, and the new name.

Instructions

Muda o nome de uma fonte do notebook.

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>",
      "fonte": "<fonte>",
      "novo_nome": "<novo_nome>"
    },
    "name": "notebook_fonte_renomear"
  }
}

Input Schema

NameRequiredDescriptionDefault
fonteYesTítulo atual (ou parte) ou id.
notebookYesId, URL ou título do notebook (o título pode ser parcial).
novo_nomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is known, but the description adds nothing beyond that: it does not say whether partial-title matches can rename the wrong source, whether titles must be unique within the notebook, 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 efficient sentence with the resource front-loaded and no waste, though its brevity leaves little room for the operational context an agent would need.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation tool with no output schema, the description leaves the agent guessing about ambiguity handling for partial titles, whether the source's other properties (citations, indices) survive the rename, and what the call returns.

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%; the schema explains that 'fonte' accepts the current title, a partial title, or an id, and that 'notebook' accepts an id, URL, or partial title. The description only implies that 'novo_nome' is the replacement title and adds no details on the partial-match or length constraints already in 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?

The description states a specific verb+resource pair ("Muda o nome de uma fonte do notebook"), which pinpoints the rename operation on a notebook source rather than on the notebook itself. This implicitly separates it from notebook_renomear and notebook_estudio_renomear, though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus notebook_renomear, notebook_estudio_renomear, or notebook_fonte_remover, and states no prerequisites such as needing the source to already exist or confirming an ambiguous partial-title match.

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