Technical reference

A defined interface to Stride operations.

Client requests enter through MCP. Stride checks access, validates the operation, and returns structured information. The client does not bypass application rules.

01 / Architecture

The protocol boundary.

The host contains the model and MCP client. Stride exposes the operations. Requests cross an authenticated connection; application permissions still apply.

Host / client / server

The host is the AI application. Its MCP client exchanges protocol messages with Stride’s MCP server. The LLM proposes operations; the host manages their execution.

Tools / resources / prompts

Tools execute operations. Resources expose context. Prompts provide reusable interaction templates. Stride’s current learner baseline exposes eight tools; additional primitives belong to the expansion plan.

Protocol / permissions

MCP defines the message exchange. Stride defines which work an identity can access and which state changes are valid. A protocol capability does not grant organization or object access.

These references describe MCP, including its newer specification. They do not establish that every protocol feature is enabled in Stride or supported by every host.

MCP / HTTPS / JSON-RPCThe protocol boundary.
MCP HOST

AI application

Claude, ChatGPT, or a command-line host.

REASONINGLLM + conversation

Proposes an operation using the task and conversation context.

PROTOCOL COMPONENTMCP client

Sends the request and returns its result to the host.

REQUEST →tools/callTool name + arguments
HTTPSMCP transportAuthenticated connection
← RESPONSEStructured resultOr an operation error
MCP SERVER

Stride

Exposes bounded learner capabilities.

01
Account scopeConnected identity + allowed access
02
Operation rulesEligible target + validated inputs
03
Recorded stateTask context, attempts + outcomes
Stride controls authorization, validation and recorded state.

Requests use the connected Stride account and its allowed capabilities. A connection does not grant unrestricted access.

The response contains authorized task context or recorded status. A successful model response alone does not establish completion.

02 / Assessment lifecycle

An attempt is not a completion.

Practice stays outside the grading flow. An eligible attempt fixes the rubric; a graded submission adds evidence, scores, and reasons. Validation and a passing result are separate checks.

ASSESSMENT / READ AND WRITE LIFECYCLEILLUSTRATIVE CONTRACT FLOW
  1. READ
  2. Read eligible work
  3. Task, criteria and native-flow links
  4. WRITE
  5. Start or recover attempt
  6. Private attempt handle + frozen rubric
  7. Attach selected evidence
  8. Chosen excerpt or supported reference
  9. Submit criterion assessment
  10. Scores + reasons + evidence links
  11. REVISE
  12. Correct inputs
  13. Respect remaining graded submits
  14. PERSIST
  15. Record the outcome
  16. Stride recomputes and persists the result
  17. Read authoritative status
  18. Recorded feedback + eligible completion
  19. Submission
  20. valid?
  21. CHECK: identity · ownership · frozen rubric
  22. CHECK: scores · evidence · remaining submits
  23. YES / RECORD
  24. NO / CORRECT
  25. RETRY THE REVIEWED SUBMISSION
  26. ASSESSMENT CONTRACT
  27. Practice stays in the LLM.
  28. Only selected evidence is attached.
  29. Submitted scores are checked by Stride.
  30. Valid does not necessarily mean pass.
  31. TIMEOUT / UNKNOWN RESULT
  32. Read status before retrying.
  33. Recover the stored outcome first.
  34. A client timeout does not prove failure.
  35. Do not infer completion from the chat.
  36. THE RECORDED STATE IS AUTHORITATIVE
  37. Private handle + frozen rubric
  38. Excerpt or supported reference
  39. Stride recomputes the result
  40. Feedback + eligible completion
  41. VALIDATION CHECKS
  42. Identity · ownership · frozen rubric
  43. Scores · evidence · remaining submits
  44. NO: revise
  45. YES
  46. VALID DOES NOT NECESSARILY MEAN PASS.

Practice stays outside the grading flow. An eligible attempt fixes the rubric; a graded submission adds evidence, scores, and reasons. Validation and a passing result are separate checks.

A client timeout does not prove failure.

03 / Current tool catalog

Operations and limits.

The learner connector supports eligible work. Native activities and challenge submission stay in Stride.

EffectOperationContract
READget_my_status
Connection status
Read your connection state and recent assessment summary.
READlist_current_work
Current work
List your current eligible Stride work.
READget_work_detail
Work details
Retrieve task context, available criteria and recorded feedback.
READfind_microlearnings
Lesson search
Find accessible microlearnings beyond the current-work list.
READget_attempt_status
Attempt status
Read the recorded assessment state and outcome.
WRITEstart_attempt
Start an attempt
Create or recover a private attempt and receive its frozen rubric.
WRITEadd_attempt_evidence
Attach evidence
Add a selected excerpt or supported reference to your attempt.
WRITEsubmit_assessment
Submit an assessment
Submit criterion scores, reasons and evidence for validation.

These are the eight active learner tool contracts. The prepared interactive and product-help packages await validation and release. Later resource, contribution and role capabilities are planned.

04 / Access and data

Access is enforced per operation.

Stride remains responsible for account scope, assessment validation, and recorded state. Each boundary has a specific effect.

01

Identity

Sign in with your own Stride account and review the connection’s access. Learner operations remain within that account’s authorized scope.

02

Evidence

Stride receives selected work, criterion scores and reasons, and the outcome. The whole conversation is not included in the connector submission.

03

Validation

Stride validates submitted scores and evidence requirements against the frozen rubric. It does not independently prove every claim in the evidence.

04

Revocation

Disconnect through connected-client controls. Revocation ends future access; it does not undo recorded work or retract prior responses from a client.

CGI Stride Connect