Skip to main content
Glama

find_learner

Read-onlyIdempotent

Identify a learner by exact email to get the ID needed for progress tools, along with registration count, completion count, and latest activity across the organization.

Instructions

Look up a learner by email, and get the id the progress tools need.

    Returns the learner's id plus lifetime counts v2 does not carry:
    `registration_count`, `completion_count` and `latest_activity` across the whole
    organization.

    The id returned works in BOTH APIs - the same value identifies this learner to
    v2's `get_student` and to `list_learner_progress`. Observed rather than
    documented, so worth re-checking if Skilljar ever changes its id scheme.

    Email match is exact, and an unknown address returns an empty list rather than
    an error - so an empty result does not prove the address is wrong.

    `total` is v1's own count of matches. v2 never provides a total for anything.

    Requires `CSA_SKILLJAR_V1_API_KEY`, a separate credential from the v2 client.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
totalNo
learnersYes
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say read-only and idempotent. The description adds substantial behavioral context: exact email matching, empty list on unknown addresses, v1's total semantics, the observed-but-undocumented id scheme, the separate v1 credential, and lifetime counts that v2 does not carry.

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?

The purpose is front-loaded, and every subsequent line adds unique, actionable information: return fields, cross-API id compatibility, edge-case behavior, and auth requirements. There is no filler or repetition.

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?

For a single-parameter lookup tool with an output schema, the description covers purpose, return contents, cross-API usage, failure behavior, credential requirements, and a caveat about id stability. Nothing an agent needs to call it correctly is missing.

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 schema provides no description for email and coverage is 0%, so the description must compensate. It does: the parameter is clearly the lookup key, and the description specifies that matching is exact, adding meaning beyond the raw schema.

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 a specific verb and resource: 'Look up a learner by email, and get the id the progress tools need.' It clearly states what the tool does and distinguishes it from sibling tools by explaining how the returned id bridges v2's get_student and list_learner_progress.

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 gives clear context: the returned id is needed by progress tools and works in both APIs, so an agent knows when to reach for this tool. It names relevant sibling outputs as destinations for the id, though it does not explicitly say 'use this instead of get_student when you only have an email.'

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CloudSecurityAlliance/csa-skilljar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server