Skip to main content
Glama

Next study option

get_next_study_action
Read-onlyIdempotent

Use this when the connected learner asks what to study next in CertArc. Returns their CertArc assessment and its link while it is unfinished, otherwise the next eligible sprint in study order and a link to its domain; the calendar may recommend another. Does not start or complete a session.

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

Input Schema

NameRequiredDescriptionDefault
programNoCertification to read. Omit for the one the learner studied most recently; every result names its certification and lists the learner's others.

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the description adds value by disclosing the fallback precedence (unfinished assessment first, then sprint in study order) and warning that a calendar recommendation may differ. What remains undisclosed is how ties or empty states are handled, which keeps it from a 5.

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?

Three sentences, front-loaded with the usage trigger before the return logic, and no filler. The middle sentence packs two branches plus a caveat into one long clause, which is dense but still parseable.

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 one optional parameter backed by a full schema description and a lightweight read-only profile, the description is nearly complete, and since no output schema exists it correctly carries the burden of explaining both return shapes. Only edge-case behavior (no assessment and no eligible sprint) is left unstated.

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

Parameters3/5

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

Schema coverage is 100% and the single 'program' parameter is fully documented in the schema, including the omit-for-most-recent default and enum values. The description never mentions the parameter, so it adds no meaning beyond the schema; baseline 3 applies.

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 pair (returns the next study action) and spells out both outcome branches: an unfinished CertArc assessment with its link, otherwise the next eligible sprint in study order with a domain link. The closing line 'Does not start or complete a session' separates it from action-taking siblings such as open_study_panel.

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?

Gives an explicit trigger: 'Use this when the connected learner asks what to study next in CertArc,' and adds a negative boundary by saying it does not start or complete a session. It hints that 'the calendar may recommend another' but never names the alternative tool, so routing is implied rather than fully specified.

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.