Skip to main content
Glama

Get course duplication status

get_course_duplication_status
Read-onlyIdempotent

Returns the current state and target course ID for a course duplication started by this user.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_course_duplication_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety bar is covered. The description adds a real behavioral detail — results are filtered to duplications started by the calling user — plus that 'target course ID' is part of the payload. It does not enumerate possible state values or terminal/failed states, which is the main thing an agent polling this needs.

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?

One sentence, no filler, front-loaded with the verb and return content. It is efficiently written, though the terseness leaves room for one more clause on task_id or state values without becoming bloated.

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-only poller with no output schema, the description covers what is returned at a high level. It omits the provenance of task_id and the set of possible states, both of which an agent needs to decide when to stop polling.

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 coverage is 0% and the single required parameter task_id is never mentioned in the description. It is unclear whether task_id comes from duplicate_course's response, whether it is a course ID or an operation ID, or what happens for unknown/stale IDs. With only one parameter, this gap was cheap to close and was not.

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?

Names a specific verb+resource: returns the current state and target course ID of a course duplication. The phrase 'started by this user' also scopes it relative to duplicate_course. It stops short of explicitly naming duplicate_course as the launch tool, so sibling differentiation is implied 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?

The precondition 'started by this user' implies when this applies (polling after a duplication is launched), but there is no explicit when-to-use statement, no guidance on repeated polling vs. one-shot calls, and no alternatives named. Guidance must be inferred.

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