Skip to main content
Glama

Padlet

by com.padlet
OverviewDiscussionsAdmin

Sync Grades to LMS

sync_grades_to_lms
Destructive

Sync all grades for a padlet to the connected LMS (e.g. Canvas, Schoology) via LTI passback.

  • Purpose: Push all existing post grades to the LMS gradebook.

  • What this tool returns: { success: true } on success; { success: false, message: "..." } on failure.

  • Only available when LMS passback is enabled on the padlet.

  • Only wall builders and admins can trigger a sync.

  • The sync may be asynchronous for padlets with many students — in that case the result will indicate async: true and the LMS will update shortly.

Input Schema

NameRequiredDescriptionDefault
wall_urlYesThe padlet's link (e.g. https://padlet.com/foo/bar-a1b2c3): the link you were given, the `wall_url` a previous call returned, or a link the user pasted. Not a breakout-room or submission link, and not a padlet id: no tool takes a wall_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / wall_url / description
      Previous value: -"The padlet's link (e.g. https://padlet.com/foo/bar-a1b2c3): the link you were given, the `wall_url` a previous call returned, or a link the user pasted. Not a breakout-room or submission link."New value: +"The padlet's link (e.g. https://padlet.com/foo/bar-a1b2c3): the link you were given, the `wall_url` a previous call returned, or a link the user pasted. Not a breakout-room or submission link, and not a padlet id: no tool takes a wall_id."
  2. Changed3 schema fields changed
    • removedInput schema / properties / wall_id
      Removed value: -{
-  "description": "The id of the padlet whose grades should be synced to the LMS.",
-  "type": "integer"
-}
    • addedInput schema / properties / wall_url
      Added value: +{
+  "description": "The padlet's link (e.g. https://padlet.com/foo/bar-a1b2c3): the link you were given, the `wall_url` a previous call returned, or a link the user pasted. Not a breakout-room or submission link.",
+  "maxLength": 2048,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "wall_id"
-]New value: +[
+  "wall_url"
+]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes beyond the annotations: it discloses the async behavior for large student counts and the { success, message, async } response shape, plus the permission prerequisite. It doesn't explain what 'destructive' risk exists (overwriting existing LMS gradebook entries) or non-idempotency beyond the annotation flags, but the added context is genuinely useful.

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?

Front-loaded with the action and scope, then structured bullets for return value, availability, and permissions; every line adds information. The 'Purpose:' bullet mildly restates the opening sentence but the rest is efficient.

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?

With no output schema, the description supplies the return shape, async caveat, precondition, and permission gate — enough for correct invocation. Minor gaps remain on failure cases and whether ungraded posts are skipped, but nothing blocking.

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 a single, well-documented wall_url parameter, so the schema does the heavy lifting. The description doesn't reference wall_url at all, adding nothing beyond what's already documented — baseline 3.

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 names a specific verb and resource: 'Sync all grades for a padlet to the connected LMS ... via LTI passback', and adds 'Push all existing post grades to the LMS gradebook', which implicitly separates it from grade_posts (which sets the grades). It never names that sibling explicitly, so the distinction is inferred rather than stated.

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?

Preconditions are stated clearly: LMS passback must be enabled and the caller must be a wall builder or admin. However, there is no guidance on when to choose this over grade_posts or whether grades must be set first, so the usage guidance stays implied.

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

All Padlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources