Skip to main content
Glama
Sign In
SWEN AI

SWEN AI

by luisroquette-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

List AI Tutorials

list_tutorials

Explore a directory of AI tutorials and guides to find learning resources for AI tools and model intelligence.

Instructions

Tutorials and guides directory. From SWEN.AI.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 30)
offsetNoPagination offset (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it only says 'Tutorials and guides directory. From SWEN.AI.' It does not disclose pagination, response format, or any other behavioral specifics beyond implying a list.

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?

The description is very short and to the point, but 'From SWEN.AI' adds provenance rather than functional info, and the noun phrase could be more grammatically complete. Still, it is two short sentences with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description is too sparse to be complete. It doesn't mention what tutorial data is returned, how pagination works, or any limitations, leaving the agent to infer from the name and schema.

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 descriptions for limit and offset, so the schema fully documents both parameters. The description adds no parameter information, matching the baseline of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Tutorials and guides directory' is a noun phrase that implies the tool lists tutorials/guides but lacks an explicit verb like 'list' or 'retrieve'. It differentiates from sibling tools by topic but does not clearly state the action or scope.

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 is provided on when to use this tool vs alternatives. The description gives no context about use cases, filtering, or relationship to sibling tools like search_news or list_ai_models.

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