Skip to main content
Glama

Niche of One Network

The Method course

course
Read-onlyIdempotent

The Method, the free Niche of One field manual, as a course: lessons in order, each with an exercise. The first 3 lessons are open to anyone; the rest need a free Niche of One sign-in (no paid plan). No lesson named: the next one (signed-in progress is kept). list true: every lesson. Best shown as a step-by-step artifact.

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

Input Schema

NameRequiredDescriptionDefault
listNo
lessonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely non-obvious behavior: the first 3 lessons are open, the remainder require a free sign-in (no paid plan), and signed-in progress is tracked. It also advises presenting the output as a step-by-step artifact, though it doesn't say what a locked lesson looks like in the response.

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?

Compact and front-loaded: what the tool is, then the access rule, then the two parameter behaviors, then the presentation hint. The telegraphic fragments ('No lesson named: the next one') are dense but parse cleanly and nothing is padding.

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?

With no output schema and only two params, the description covers what an agent needs: ordered lessons with exercises, gating by sign-in, and the two modes. It stops short of describing whether an individual lesson returns exercise text or just metadata, which is the one remaining uncertainty for calling it correctly.

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 coverage is 0%, so the description carries the full burden and largely does: 'lesson' means a specific named lesson, absent means the next one; 'list true' means every lesson. The numeric bounds (1-999) and the interaction between list=true and lesson are not addressed, keeping it below 5.

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 states a concrete resource and scope: 'The Method ... as a course: lessons in order, each with an exercise,' so an agent knows it retrieves ordered lesson content rather than submitting work. It does not explicitly name a sibling (e.g., course_submit) as the place exercises are sent, so differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly explains the two usage modes: omit the lesson to get 'the next one' and pass list=true for 'every lesson,' which is actionable routing guidance. What's missing is explicit when-not guidance and any mention of when to hand off to course_submit or academy_lesson.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources