Skip to main content
Glama

Get lesson upload status

get_lesson_upload_status
Read-only

Returns the grant-bound upload or video-processing status. Stop polling at ready, failed, or expired.

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": {
      "upload_handle": "<upload_handle>"
    },
    "name": "get_lesson_upload_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_handleYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the description carries a lighter burden. It still adds genuinely new context: 'grant-bound' signals the handle-scoped authorization model, and the terminal-state list (ready, failed, expired) tells the agent the lifecycle has a defined end, including an expiry outcome not visible in any structured field.

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?

Two sentences, zero waste, with the core identity front-loaded and the actionable polling instruction second. Nothing is repeated from the title or schema.

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

Completeness3/5

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

For a one-parameter read tool with annotations covering the safety profile and no output schema, this is close to adequate. The gap is the response surface: the agent learns three terminal states but not what non-terminal states look like or how failures (e.g. an invalid or foreign handle) manifest.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description must compensate and largely does not. 'Grant-bound' hints that upload_handle is an authorization-scoped token rather than an opaque ID, but it never states where the handle comes from or what format it takes.

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 gives a specific verb and resource: it 'returns the grant-bound upload or video-processing status.' That distinguishes it from build/duplication status siblings and from the create_*_upload_session tools, though it does not name an alternative explicitly.

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?

Usage is only implied: it is clearly a polling tool used after an upload session is created, reinforced by 'Stop polling at ready, failed, or expired.' There is no explicit statement of when to prefer this over get_library_upload_status or get_course_build_status, so the agent must infer routing from the tool name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources