Skip to main content
Glama

Modo quiz

set_quiz

Toggle quiz mode on a Google Form to assign grades or revert to a regular form.

Instructions

Liga ou desliga o modo quiz (com notas) de um formulário.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formIdYesID do formulário
isQuizYestrue para virar quiz, false para voltar a formulário comum
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does mention the tool can turn quiz mode on or off (implying reversibility) and that quiz mode includes grades ('com notas'), but it omits permission requirements, effects on existing responses or grading, and any validation behavior.

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, front-loaded sentence that states the action and key qualifier ('with grades'). Every word contributes to understanding, with no filler or redundant repetition of the tool name.

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 boolean setter with two fully described parameters, the description plus schema is largely complete. A slight deduction is made because there is no output schema or mention of the return value, and no explicit usage guidance relative to sibling tools.

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%: both formId and isQuiz have descriptive schema text. The description does not add new parameter details, but the schema already fully explains the inputs, so a baseline score of 3 is appropriate.

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 a specific action: 'Liga ou desliga o modo quiz (com notas) de um formulário' (turns on/off quiz mode with grades for a form). It names the resource (form) and the mode being toggled, distinguishing it from sibling tools like set_publish or update_form_info.

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 description implies the tool is used when you need to enable or disable quiz mode on a form, but it does not explicitly state when to use it over alternatives or provide exclusion criteria. Sibling tool names (e.g., set_publish) suggest the distinction, but the description itself offers no direct guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/claude-book/mcp-server-google-forms'

If you have feedback or need assistance with the MCP directory API, please join our Discord server