Skip to main content
Glama
Sign In
LessonLab MCP Server

LessonLab MCP Server

by rocnubie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_official_links

Fetch the canonical list of official LessonLab links, including website, support, and documentation, to access verified URLs directly.

Instructions

Return the canonical list of official links for LessonLab (website, support, docs when available).

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": "get_official_links"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 burden. It mentions 'when available' for docs, indicating possible variability, but does not disclose other behaviors like caching, latency, or data freshness. The description adds minimal behavioral context beyond the obvious.

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 concise sentence that front-loads the core action and resource. Every word is necessary with no redundancy. It is a model of brevity.

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?

Given the tool's simplicity (no parameters, no output schema, no annotations), the description adequately covers the purpose. It mentions the types of links and the variability of docs. However, it could be slightly improved by hinting at the return format or purpose of having the canonical list.

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 tool has zero parameters and schema description coverage is 100%, so the baseline is 3. The description does not add parameter-specific information, but none is needed. It effectively describes the output but not the return structure.

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 'Return the canonical list of official links for LessonLab (website, support, docs when available).' It specifies the verb 'Return', the resource 'official links for LessonLab', and the types of links. This distinguishes it from sibling tools like get_lesson_workflow and get_pricing, which serve different purposes.

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. The description only states what it does, without mentioning when not to use it or comparing with siblings. For a simple tool, this lack of usage context lowers the score.

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