Skip to main content
Glama
Sign In
cint MCP Server

cint MCP Server

by pennyleans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cint_list_curriculum

List available cint University lessons from CU-000.2 to CU-401.2, optionally filter by course ID and include detailed objectives.

Instructions

List available cint University lessons (CU-000.2 to CU-401.2).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cint_list_curriculum"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseNoCourse ID filter (e.g. 'CU-000', 'CU-101', 'CU-201', 'CU-301', 'CU-401')
verboseNoIf true, include detailed lesson objectives

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'List' implies a safe read, but the definition says nothing about pagination, result ordering, whether the course filter is required to narrow output, or permission 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?

A single, front-loaded sentence with no wasted words. It is efficient, though arguably too terse for a tool with zero annotations.

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 annotations and no output schema, the description should compensate more: it does not explain default behavior (all lessons when 'course' is omitted) or the shape of results. Adequate to identify the tool, but thin for calling it confidently.

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%, with both 'course' (with example IDs) and 'verbose' fully documented in the schema, so the baseline of 3 applies. The description adds no parameter-level meaning beyond noting the overall ID scope.

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 specific verb ('List') and resource ('cint University lessons') with a concrete ID range (CU-000.2 to CU-401.2). It is clearly distinct in resource from siblings like cint_get_recipe or cint_get_doc, though it never names a sibling explicitly.

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?

The description offers no when-to-use guidance, no prerequisites, and no pointer to an alternative tool (e.g. cint_get_doc for a single lesson). The agent must infer the intended context entirely.

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