Skip to main content
Glama
Sign In
FINKI Courses MCP

FINKI Courses MCP

by mahmutmft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_course

Read-onlyIdempotent

Retrieve sections and resource links from an enrolled course main page using a course ID to find authorized materials and their source URLs.

Instructions

Browse sections and resource links rendered on an enrolled course main page.

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": {
      "courseId": "<courseId>"
    },
    "name": "get_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description contributes the meaningful detail that results are rendered page content (implying page-scoped, presentation-oriented output) but says nothing about size, paging, or what happens for a non-enrolled course.

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 front-loaded sentence with no filler; the core action and scope arrive immediately. It is arguably too terse for a tool with no output schema, but nothing is wasted.

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?

With no output schema, the description has to convey what comes back. It does so only at a high level ('sections and resource links rendered'), leaving the actual structure and any error behavior for an unenrolled or missing course undisclosed.

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 single courseId parameter has 0% schema description coverage, so the description must carry the load. It does add the constraint that the id refers to an *enrolled* course, which is real meaning beyond the bare integer in the schema, but it gives no format or source for the identifier.

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?

States a concrete verb ('Browse') and resource ('sections and resource links rendered on an enrolled course main page'), so an agent knows it retrieves rendered course-page content. It is specific enough to separate from a plain course fetch, but it never names or contrasts list_courses/search_course, so sibling differentiation is left to inference.

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: 'enrolled course' hints at the prerequisite that the courseId must belong to a course the caller is enrolled in. There is no explicit statement of when to choose this over list_courses or search_course, nor any when-not guidance.

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