Skip to main content
Glama
Sign In
LearnOneTech MCP

LearnOneTech MCP

by arifaidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_articles

Retrieve a paginated list of recent LearnOneTech articles, optionally filtered by category, to browse public technology and troubleshooting content.

Instructions

List recent LearnOneTech articles with pagination.

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_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo
category_idNoOptional WordPress category ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

There are no annotations, so the description must carry the behavioral disclosure. 'List' implies a read-only operation, and 'recent' plus 'paginaation' provides some ordering/pageination context. However, it does not mention response shape, authorization, or whether the list is limited to published content.

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 sentence with no redundant words; the action and resource appear first. It is appropriately terse, though it could have added sibling differentiation without bloating.

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?

With no output schema and no annotations, the description leaves important details uncovered: returned fields, ordering semantics, and how pagination is represented in responses. The optional category filter is only discoverable via schema inspection, and there is no guidance on how this tool relates to search_articles.

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 description's mention of pagination adds meaning to the page and per_page parameters, which lack schema descriptions. It does not mention category_id, but that parameter already has a clear schema description ('Optional WordPress category ID'), so the schema covers that gap.

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?

The description specifies a clear verb ('List'), a resource ('LearnOneTech articles'), and scope ('recent', 'pagination'), which lets an agent identify what the tool does. It is distinct from search_articles and get_article because it is a listing operation, though it does not explicitly contrast with siblings.

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 given for when to choose list_articles over search_articles, get_article, or list_categories. The description does not state whether 'recent' means all articles, published-only articles, or how pagination interacts with filtering.

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