mcp-server-google-forms

Reordenar pergunta

move_question

Reorder a Google Form item by specifying the form ID, current position, and new position. Positions are zero-based and include all items.

Instructions

Move um item de uma posição para outra. As posições contam TODOS os itens (0 = primeiro) — confira antes com get_form.

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": {
      "formId": "<formId>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "move_question"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Nova posição desejada
`from`	Yes	Posição atual do item
`formId`	Yes	ID do formulário

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Aug 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds important details not in the schema: positions count ALL items and are 0-based. However, it does not explain side effects like shifting of other items or the nature of the response, leaving some behavioral aspects implicit.

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?

The description is a single concise sentence with a parenthetical caveat, front-loading the action and giving essential positional context. Every word earns its place, with no redundancy or fluff.

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?

For a simple 3-parameter reorder tool with no output schema, the description covers the core action, position semantics, and a practical prerequisite. It could mention impact on other items or return behavior, but given the tool's simplicity and the guidance to use get_form, it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides 100% parameter descriptions, so the baseline is 3. The description adds meaning by clarifying that 'from' and 'to' refer to positions counting all items from 0, which is not fully specified in the schema descriptions. This extra context enhances parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool moves an item from one position to another, with a specific verb and resource. It distinguishes from siblings like delete_question and update_question by focusing on reordering. The title 'Reordenar pergunta' reinforces this purpose.

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?

The description provides a clear prerequisite by advising to check with get_form before moving, which is valuable context for using the tool correctly. It does not explicitly exclude alternatives or mention when not to use, but since no other sibling tool does reordering, the usage context is sufficiently implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server