Skip to main content
Glama
Sign In
getcourse-mcp

getcourse-mcp

by skiddgoddamn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gc_set_order_status

Updates a deal's status, including cancellation with a reason ID to handle duplicate orders.

Instructions

Изменить статус сделки (напр. отменить дубль: status=cancelled + cancelReasonId).

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": {
      "dealId": "<dealId>",
      "status": "<status>"
    },
    "name": "gc_set_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
dealIdYesID сделки (из gc_find_orders или URL /sales/control/deal/update/id/<id>).
statusYesНовый статус сделки.
cancelReasonIdNoID причины отмены для status=cancelled (напр. «Дубль заказа»=54347 на li-ft.ru).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as whether the operation is destructive, reversible, or requires authentication. For a mutation tool, this is a significant gap.

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 sentence that efficiently conveys the action and a key use case. No redundant information, and the core purpose is front-loaded.

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 simple mutation tool, the description is minimally adequate but lacks details on return values, error handling, or side effects. Without an output schema, more context would help, especially for status changes beyond cancellation.

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

Parameters4/5

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

Schema description coverage is 100%, but the description adds valuable context by explaining the use of cancelReasonId and providing a concrete example ID. This enhances understanding beyond the schema, though other parameters are not elaborated.

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 clearly states the tool changes deal status and provides an example (cancel duplicate). It distinguishes itself from mutation tools like gc_refund_order or gc_create_order, though it could be more explicit about its scope.

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 explicit guidance on when to use this tool versus alternatives like gc_refund_order or gc_find_orders. The example implies usage for cancellation, but no when-not or prerequisites (e.g., needing dealId from gc_find_orders).

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

Deploy Server

Other Tools