Skip to main content
Glama
Sign In
getcourse-mcp

getcourse-mcp

by skiddgoddamn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gc_find_offers

Search for active sale offers by name substring, returning ID, price, and relevance to use when creating orders.

Instructions

Найти офферы продажи по подстроке названия (id + цена + актуальность). Нужно для gc_create_order.

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": {
      "query": "<query>"
    },
    "name": "gc_find_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesПодстрока названия оффера (например «Формула AI Полный доступ»).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool searches by substring and returns id, price, and relevance. It does not mention side effects, permissions, or rate limits, but given it's a read search, this is adequate.

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 two sentences long, concise and to the point. The second sentence could be integrated, but there is no extraneous information.

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?

For a simple tool with one parameter and no output schema, the description is fairly complete: it explains the action, the search method, the return values, and the use case. It lacks details on pagination or edge cases, but is sufficient.

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?

The only parameter 'query' has a description in the schema and the tool description provides an example. With 100% schema coverage, the description adds marginal value, meeting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: find offers by substring, returning id, price, and relevance. It also notes it's needed for gc_create_order, distinguishing it from sibling search tools like gc_find_orders and gc_find_user.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by stating 'Нужно для gc_create_order', indicating it's used before order creation. It does not explicitly list when not to use or alternatives, but the context is clear enough for an AI agent.

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