Skip to main content
Glama

List language pairs

language_pairs_list
Read-onlyIdempotent

Lists the Memrise language pairs on an account and returns each course id, so you can set MEMRISE_LANGUAGE_PAIR_ID when the account has multiple courses.

Instructions

List the Memrise courses (language pairs) of this account. The id of a pair is the value for MEMRISE_LANGUAGE_PAIR_ID when the account has more than one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds the scope constraint that results are limited to 'this account' and that ids feed a specific config variable. It says nothing about result size, pagination or whether all pairs or a subset are returned, which keeps it at a solid 3 with annotations doing the heavy lifting.

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, zero filler, and the core purpose is front-loaded before the supplementary id/config note. Every clause earns its place.

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 parameters and no output schema, the description carries the burden of explaining what comes back; it does state that courses/language pairs are listed and identifies the `id` field. It omits any mention of other fields per pair (e.g. names) or ordering, which is a minor gap for such a simple tool.

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?

The tool takes zero parameters, so there is no input semantics to document; the baseline of 4 applies. The description's only field-level detail concerns the output `id`, which is a bonus rather than required parameter guidance.

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 gives a specific verb and resource ('List the Memrise courses (language pairs) of this account') and usefully disambiguates terminology by equating courses with language pairs. It is clear what the tool returns, though it does not name any sibling to contrast scope with (e.g. learnables or scenarios), so sibling differentiation is only implicit through the resource noun.

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?

The second sentence supplies real usage context: the returned `id` is the value expected for MEMRISE_LANGUAGE_PAIR_ID when the account has more than one pair. That effectively tells the agent why and when to call this tool. It stops short of explicit exclusions or naming alternatives, so not a 5.

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