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

smart-coding-mcp

by cbuntingde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

recall_lessons

Retrieve the most relevant past lessons using free-text search. Empty query returns recent lessons for quick access.

Instructions

Recall top-k lessons matching query (FTS5 retrieval).

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

Input Schema

NameRequiredDescriptionDefault
kNoNumber of lessons to recall (1..50).
queryNoFree-text search over summary/evidence/tags. Empty string returns the most recent lessons.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided; description states FTS5 retrieval but does not explicitly disclose read-only nature or side effects. Adequate but could be more explicit.

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?

Single, front-loaded sentence with no fluff. Every word adds value.

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 low parameter count, schema coverage, and presence of output schema, the description is sufficient. Slight gap: no mention of output format or return structure.

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 covers all parameters (100% coverage). Description adds minimal value: 'FTS5 retrieval' and empty query behavior. Baseline 3 justified.

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?

Clearly states action (recall), resource (lessons), and method (FTS5 retrieval). Distinct from sibling 'recent_lessons' by emphasizing search matching.

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?

Implies usage for search-based retrieval versus recency, but no explicit when-to-use or when-not-to-use compared to siblings like 'recent_lessons'.

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