Skip to main content
Glama

Look up learner words

learnables_lookup
Read-onlyIdempotent

Check whether a learner has met specified Portuguese terms despite case, accents, punctuation and leading articles; optionally limit results to fully learned or known words.

Instructions

Check whether the learner has met each term (a Portuguese word or phrase). Matching ignores case, accents, punctuation and a leading article. Each result has met, match ("exact", "in_sentence" or "none"), items (matching words) and in_sentences (words inside longer phrases). state: 'any' (default) = every word you have met; 'fully_learned_or_known' = only fully learned or already-known words. If some lesson details cannot be fetched, results are still returned without those lesson links and a warnings field names the failed lesson ids. The first call in a fresh process with a cold cache is noticeably slower because every completed lesson is fetched once; later calls are fast.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "terms": "<terms>"
    },
    "name": "learnables_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoany
termsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond annotations by disclosing normalization rules (case, accents, punctuation, leading article), partial-failure behavior with a warnings field listing failed lesson ids, and a cold-cache performance caveat on first call. Minor gaps remain, such as whether results are truncated at the 500-term limit, but the behavioral picture is unusually rich for a read-only tool.

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?

Front-loads the core purpose, then layers matching rules, result fields, the state filter, failure behavior, and the performance caveat in a logical order. A few sentences are dense and could be split, but nothing is redundant.

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

Completeness5/5

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

With no output schema, the description takes responsibility for naming the returned fields (met, match, items, in_sentences, warnings) and explaining their meanings. Combined with the normalization and partial-failure notes, an agent has everything needed to call the tool and interpret its output.

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 must carry the load, and it does: it explains both state values and the default, and clarifies that terms are Portuguese words or phrases. It omits the array size bounds (1-500) and any guidance on batching large term lists.

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?

States a specific verb and resource: check whether the learner has met each supplied term. The clarification that a term is a Portuguese word or phrase scopes it away from sibling tools like learnables_list and scenario_learnables, which deal with lists rather than membership checks.

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?

Usage is implied by describing what the tool checks and how the state filter narrows results, but it never says when to prefer this over learnables_list or scenario_learnables, nor when a bulk lookup is inappropriate. An agent can infer the use case but gets no explicit routing or exclusions.

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