Skip to main content
Glama
Sign In
LearnOneTech MCP

LearnOneTech MCP

by arifaidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_article

Retrieve a LearnOneTech article by numeric post ID or exact slug. Get cleaned readable text plus canonical URL for quick reference.

Instructions

Retrieve a LearnOneTech article by numeric WordPress post ID or exact slug. Returns cleaned readable text plus the canonical URL.

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

Input Schema

NameRequiredDescriptionDefault
idNo
slugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden, and it does state the key output behavior: returns cleaned readable text plus the canonical URL. It does not discuss not-found behavior or authentication, but for a simple read-only fetch it gives enough behavioral context.

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?

Two short sentences front-load the action and identifier options, then state the return value. There is no filler and every clause contributes useful information.

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?

For a two-parameter fetch tool with no output schema, the description adequately covers the resource, lookup keys, and return content. It lacks explicit not-found behavior and a clear 'provide one of id or slug' note, but it is otherwise complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description's mention of 'numeric WordPress post ID' and 'exact slug' adds real meaning beyond the raw property names id and slug. It could clarify precedence if both are supplied or note that one is required, but both parameters are otherwise meaningfully explained.

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 opens with the verb 'Retrieve' and names the resource ('LearnOneTech article'), then specifies the two lookup keys: numeric WordPress post ID or exact slug. This makes it distinct from sibling search/list tools, which are not single-article lookups by identifier.

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?

The phrase 'by numeric WordPress post ID or exact slug' implies this tool is for callers who already have one of those identifiers. It does not explicitly state when to prefer this over search_articles or list_articles, nor does it give exclusions or alternative routing.

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