Opendart Akademi

Get course details

get_course_details

Read-onlyIdempotent

Get the details of one Opendart course: official title, short description (topics, format, total hours as published on the course page), Turkish and English page URLs and related topic guides. Use after search_courses or when the user names a course. Does not include prices or dates; call get_course_schedule for announced start dates. TR ipucu: eğitim sayfasının başlığı, özeti ve adresi; ör. course "Flutter", "Java Spring Boot", "DevOps".

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": {
      "course": "<course>"
    },
    "name": "get_course_details"
  }
}

Input Schema

Name	Required	Description	Default
`course`	Yes	Course name, keyword or opendart.com course URL, e.g. "Flutter", "Java", ".NET Core", "DevOps", "Claude n8n". / Eğitim adı.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the exact payload shape and the negative boundary against schedule data. It stops short of saying what happens when the course name is ambiguous or not found, which matters for a keyword/URL lookup.

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 capability, then usage, then the exclusion, then the return contents — a sensible order with no filler in the English portion. The trailing Turkish line largely re-states the return fields and examples already given, which is mild redundancy (though plausibly intentional for a Turkish-language product).

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 correctly compensates by listing the returned fields, and it covers routing and scope limits. What's missing is failure/ambiguity behavior for a fuzzy single-string lookup. That is the only material gap for a tool this simple.

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% and the single `course` parameter already documents that it accepts a name, keyword or opendart.com URL with examples. The description's examples ("Flutter", "Java Spring Boot", "DevOps") restate rather than extend that. Baseline 3 applies since the schema does all the parameter work.

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?

Opens with a specific verb+resource ("Get the details of one Opendart course") and enumerates exactly what comes back: title, short description with topics/format/total hours, TR/EN URLs, related topic guides. It explicitly bounds the scope (no prices or dates), which separates it cleanly from get_course_schedule.

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

Usage Guidelines5/5

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

States both entry conditions ("after search_courses or when the user names a course") and an explicit exclusion with the correct alternative ("Does not include prices or dates; call get_course_schedule for announced start dates"). The agent has no ambiguity about when to pick this tool versus its siblings.

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

All Opendart Akademi tools Inspect

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

Need Help?