Skip to main content
Glama
Sign In
smart-coding-mcp

smart-coding-mcp

by cbuntingde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

recent_lessons

Retrieves a chronological list of the most recent lessons. Specify the number of lessons to return to keep your session context up to date.

Instructions

Return the most-recent lessons (chronological).

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent lessons to list (1..100).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'most-recent lessons (chronological)' without explaining return format, pagination, read-only nature, rate limits, or what 'lessons' includes. This is insufficient for a tool with no annotations.

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, front-loaded sentence with no unnecessary words. Every part is essential: verb, resource, ordering. Extremely concise.

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?

Given that an output schema exists and there is only one parameter, the description is minimally adequate but could provide more context about the returned data, default behavior, or time scope. However, it does not mislead and covers the core functionality.

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% for the single 'limit' parameter, which already has a clear description. The tool description adds no extra value beyond the schema, so baseline 3 is appropriate.

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 'Return the most-recent lessons (chronological)' clearly states the verb ('Return'), the resource ('lessons'), and the ordering ('most-recent', 'chronological'). It differentiates from sibling tools like 'recall_lessons' (likely search) and 'record_lesson' (write), making purpose unambiguous.

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 guidance on when to use this tool vs. alternatives (e.g., 'analyze_path', 'by_category'). No mention of prerequisites, context, or exclusions. The agent lacks information to choose optimally among siblings.

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