Skip to main content
Glama

edubase_post_quiz_transfer

Transfer a quiz to a user by specifying the quiz and user identification strings.

Instructions

Transfer Quiz to user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quizYesQuiz identification string
userYesuser identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesthe user identification string
contentYes
successYesoperation was successful
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description adds no extra behavioral context. It correctly implies mutation ('Transfer') but does not disclose potential side effects like ownership changes or permission impacts.

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?

The description is a single sentence, extremely concise. However, it could be slightly improved by front-loading key action details like 'Transfers ownership of a quiz to a user.'

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?

Given the existence of many similar transfer tools (e.g., class, course, exam transfers), the description lacks distinguishing details. It does not explain what 'transfer' means operationally, nor does it mention expected outcomes or output schema (though optional). The tool's openWorldHint=true suggests dynamic behavior, but no context is provided.

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 100% with descriptions for both parameters ('Quiz identification string', 'user identification string'). The description adds no further meaning beyond the schema, so baseline score of 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?

The description 'Transfer Quiz to user' clearly identifies the action (transfer) and the resource (quiz) and target (user). It distinguishes from sibling tools like edubase_post_class_transfer by specifying the resource. However, it does not elaborate on what 'transfer' entails (e.g., ownership change).

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?

No guidance is provided on when to use this tool versus alternatives, such as other transfer tools or when prerequisites like permissions are needed. The description leaves the agent to infer usage context.

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/EduBase/MCP'

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