A
licenseA
qualityD
maintenanceEnables browsing and preparing study materials from local documents (PDF, Markdown, text, Word) via tools for overview, search, reading, chunking, and quiz generation.
9
MIT
Studocu
by com.studocu
Server Details
Find Studocu study documents, courses and institutions, and manage study projects and quizzes.
Ownership verified
- Status
- Healthy
- Uptime
- 99.8% over 22 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A3.7/5.0
Scored across 18 tools
Disambiguation4/5
Tools target distinct resources and actions, and descriptions explicitly disambiguate close pairs like get-context vs get-project-state and request-creation vs write-artifact. The only mild overlap is read-artifact vs read-detached-document (both read document text), but the descriptions clarify project-scoped vs standalone.
Naming Consistency4/5
Most tools follow a predictable verb_noun kebab-case pattern (search-courses, create-project, read-artifact, write-memory, delete-memory). Minor deviations like agent-os-session and request-creation are noun-phrased but still readable and unambiguous.
Tool Count4/5
18 tools is slightly heavy but each maps to a distinct capability across search, projects, artifacts, memories, and courses. Reasonable for the server's breadth, though a couple could be consolidated.
Completeness3/5
Core flows (create/update projects, add sources, write/read artifacts, memory CRUD, search) are covered, but there is no delete-project or remove-document-source, and no artifact deletion, leaving lifecycle dead ends. A delete/session-surface gap will occasionally force workarounds.
Available Tools
18 toolsadd-document-sourcesAdd Studocu Document SourcesAIdempotentInspect
Attach up to 10 Studocu documents from search-documents to a project as project sources. Returns the added sources with their studocu:// ids; compare with document_ids if some are missing.
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | UUID of the project that should receive the Studocu documents. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context. | |
| document_ids | Yes | 1 to 10 different positive integer Studocu document ids from search-documents (documents[].id). Example: [17, 42]. |
Output Schema
| Name | Required | Description |
|---|---|---|
| sources | Yes | |
| project_id | Yes |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing the return shape (added sources with studocu:// ids) and the partial-failure behavior — some ids may silently not be added, detected by diffing against document_ids. It does not explain why an id might fail (invalid, inaccessible, duplicate), 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.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no waste. The action and its limit are front-loaded, and the verification hint follows in the second sentence where it is most useful.
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?
For a 2-parameter mutation tool with full schema coverage, an output schema, and safety annotations, the description covers the essential agent-facing concerns including the silent-partial-success case. What remains unstated (root causes for missing documents, duplicate handling despite idempotentHint) is minor but not entirely negligible.
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 description coverage is 100%, so both project_id and document_ids are already fully documented with examples and provenance. The description reinforces that document_ids come from search-documents, but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.
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?
Specific verb (attach), specific resource (Studocu documents), specific destination (a project as project sources), plus a hard limit of 10. It also implicitly distinguishes itself from search-documents by naming that tool as the source of the ids, so an agent can tell the two apart without opening a schema.
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 establishes the workflow context (documents come from search-documents) and the cardinality constraint, which tells an agent when this tool applies. There is no explicit 'do not use when' or comparison against alternatives such as write-artifact or read-detached-document, so it stops short of a full routing guide.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
agent-os-sessionCheck Studocu Sign-inARead-onlyIdempotentInspect
Show who the current Studocu sign-in belongs to: authenticated, subject, clientId, and scopes. Use only to check that login worked.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| scopes | Yes | |
| subject | No | |
| clientId | Yes | |
| authenticated | Yes |
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the set of identity fields surfaced, but says nothing about what happens when no sign-in exists (error vs. authenticated=false), so added value is modest.
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: the first states what is returned, the second states the permitted use. The scope constraint is front-loaded where it matters.
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 zero parameters, rich annotations and an output schema, the description covers what the agent needs to choose and call it. The only real gap is unauthenticated/failure behaviour, which is neither in the description nor guaranteed by the schema.
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 nothing to disambiguate and the baseline is 4. The description correctly implies a parameterless call by describing only the current session.
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 names a specific verb ("Show") and resource ("the current Studocu sign-in") and enumerates the identity fields returned (authenticated, subject, clientId, scopes), so the agent can tell it is an identity/session inspection tool. It does not explicitly contrast itself with near-neighbours like get-context or get-project-state, which keeps it from a 5.
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 clause "Use only to check that login worked" gives an explicit usage boundary and implicitly rules out using it as a general context fetcher. It stops short of naming the alternative tool an agent should reach for when it actually wants project/course context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
create-projectCreate Studocu ProjectAInspect
Create a new project. Every field is optional. Returns project_id for add-document-sources, write-artifact, and request-creation.
| Name | Required | Description | Default |
|---|---|---|---|
| emoji | No | Icon text, usually an emoji. Example: "📚". Omit to leave the icon unset. | |
| title | No | Name, 1-255 characters, with at least one non-space character. Example: "Biology midterm". Omit to create the project without a name; the returned title is then "Untitled project". | |
| course_id | No | Positive integer course id from search-courses. Example: 1581710. The course is checked before the project is created; an unknown id creates nothing. Omit to leave the project unlinked. |
Output Schema
| Name | Required | Description |
|---|---|---|
| emoji | Yes | |
| title | Yes | Agent-displayable project title. Null Alpha names become "Untitled project". |
| course_id | Yes | |
| is_mobile | Yes | |
| project_id | Yes | UUID string in 8-4-4-4-12 hexadecimal form. Example: 11111111-1111-4111-8111-111111111111. |
| institution_id | Yes |
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this is a non-readonly, non-destructive, non-idempotent create, so the safety profile is covered. The description adds real value by disclosing the return contract (project_id) and its role in a tool chain, but says nothing about permissions, visibility of the new project, or failure behavior beyond the schema.
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 short sentences, verb-first and front-loaded, with the chaining hint last. "Every field is optional" is marginally redundant against the schema's empty required list but still aids fast scanning.
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?
For a three-optional-parameter creator with annotations and an output schema, the description covers purpose, optionality, and downstream consumption; return shape needn't be explained. Only preconditions (course validation, permissions) are left to the schema.
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 description coverage is 100%, with each parameter carrying examples, bounds, and omit-behavior, so the schema does the heavy lifting. The description only adds "every field is optional," which restates the required-list, so the baseline 3 applies.
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?
"Create a new project" gives a specific verb and resource, and the name/title distinguish it from update-project and get-project-state. It stops short of explicitly naming those siblings, so the differentiation is implied rather than stated.
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?
The description implies usage by naming the downstream tools (add-document-sources, write-artifact, request-creation) that consume the returned project_id, making this the workflow entry point. It never says when *not* to use it — e.g. versus get-project-state to reuse an existing project — so the guidance is implied rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
delete-memoryDelete Studocu Agent MemoryBDestructiveIdempotentInspect
Delete one saved memory for this learner, chosen by project_id and kind.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | Kind of the memory to delete. Example: "study_preference" or "project_learning_context". | |
| project_id | No | UUID of the project memory to delete, or null. Example: 11111111-1111-4111-8111-111111111111. Omit or null to delete a learner-wide memory. |
Output Schema
| Name | Required | Description |
|---|---|---|
| kind | Yes | Memory kind that was deleted. |
| userId | Yes | Owner of the deleted memory document. |
| deleted | Yes | Always true when the delete succeeds. |
| projectId | Yes | Owning project UUID, or null for global memory. |
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds that exactly one memory is deleted and that it is learner-scoped, but it does not explain irreversibility, behavior when the memory does not exist, or other consequences beyond what the annotations provide.
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 description is a single front-loaded sentence with no wasted words. It states the operation and selection criteria immediately.
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?
For a simple two-parameter deletion tool with full schema coverage, rich annotations, and an output schema, the description is nearly sufficient. It could be slightly more complete by stating whether deletion is permanent or by naming the complementary memory tools, but no critical calling information is missing.
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 description coverage is 100%, and the schema already explains that project_id may be null to delete a learner-wide memory. The description references both parameters but adds no format, default, or selection detail beyond the schema, so the baseline of 3 applies.
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 states a specific verb and resource: delete one saved memory, scoped to this learner, and identifies that the memory is selected by project_id and kind. It is clear apart from siblings like read-memory and write-memory by its name and operation, though it does not explicitly contrast itself with them in the text.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'chosen by project_id and kind' explains selection, but there is no explicit guidance on when to use this tool versus read-memory or write-memory, nor are prerequisites or exclusions stated. The agent must infer usage from the name and schema alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get-contextGet Learner ContextARead-onlyIdempotentInspect
Load the learner's profile, followed courses, and projects. Use get-project-state for what is inside a project. Per-topic practice scores are included only when one course is in scope; otherwise use get-course-mastery.
| Name | Required | Description | Default |
|---|---|---|---|
| course_id | No | Return only this course and its projects. Numeric id or the same id as text. Example: 1581710 or "1581710". Omit to include every followed course. | |
| project_id | No | Return only this project. Example: "11111111-1111-4111-8111-111111111111". From an earlier get-context or create-project result. Omit to include the learner's projects. | |
| active_only | No | Optional true or false. It is echoed on the response and does not change which courses or projects are returned. Omit it. | |
| recent_only | No | Optional true or false. It is echoed on the response and does not change which courses or projects are returned. Omit it. |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | |
| aggregates | No | |
| generated_at | Yes | |
| prompt_views | No | |
| requested_filters | Yes | |
| context_schema_version | Yes |
TDQS
A4.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely non-obvious behavior beyond them: per-topic practice scores appear conditionally, only when exactly one course is in scope. It stops short of describing result size or pagination, but the output schema is present to carry return-shape details.
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?
Three tight sentences: the primary behavior first, then the two sibling exclusions. Every sentence carries routing or scoping information; nothing is restated from the schema or annotations.
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 an output schema covering return values and full parameter documentation, plus clear sibling routing, an agent has what it needs to call this correctly. The only residual gap is that the description never mentions the no-op nature of active_only/recent_only, leaving the agent to discover that from the schema.
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 coverage is 100%, so the baseline is 3, but the description earns above that by explaining the semantic consequence of course_id scoping on the returned payload. It does not address the unusual active_only and recent_only no-op parameters, though the schema already documents them as echoed values.
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 set: 'Load the learner's profile, followed courses, and projects.' It then explicitly names what this tool does NOT cover (project internals, per-topic mastery), so an agent can distinguish it from get-project-state and get-course-mastery without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit routing in both directions: use get-project-state for what is inside a project, and use get-course-mastery when per-topic practice scores span more than one course. The condition that selects each alternative is stated, not implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get-course-masteryGet Course Practice ScoresBRead-onlyIdempotentInspect
Return the learner's practice scores (0-100) for the topics they have practised in one course. An empty list means no practice yet.
| Name | Required | Description | Default |
|---|---|---|---|
| course_id | Yes | Numeric course id from search-courses or get-context. Example: 1581710. A numeric string such as "1581710" is accepted. |
Output Schema
| Name | Required | Description |
|---|---|---|
| course_id | Yes | Course id whose mastery was loaded, matching followed_courses.course_id. |
| topic_masteries | Yes | Topics the learner has already practised. Empty means this course was loaded and they have not practised yet. |
TDQS
B3.4/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. The description contributes the score scale (0-100) and, importantly, the empty-list-means-no-practice semantics — genuinely useful behavioral context, though it does not mention auth needs or rate limits.
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 with zero filler; the core purpose is front-loaded and the empty-result caveat follows cleanly. 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?
An output schema exists, so return-value structure needn't be explained, yet the description still adds the score scale and the empty-list interpretation. For a single-param read-only tool this is close to complete; only the routing against sibling course tools is missing.
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 description coverage is 100% and the single course_id param is fully documented in the schema (source, example, string coercion). The description adds nothing about the parameter, so the baseline 3 applies.
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 states a specific verb ('Return') and resource ('practice scores') with a clear scope ('for the topics they have practised in one course'). It is distinguishable from get-course-syllabus by the 'mastery/scores' framing, though it never names that sibling explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It establishes the input context (one course) but offers no guidance on when to reach for this versus get-course-syllabus or get-context, and no preconditions or exclusions. The agent must infer the selection rule from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get-course-syllabusGet Course SyllabusARead-onlyIdempotentInspect
Return Studocu's generated outline for a course as markdown. If none exists yet, the call returns an error; try again in a few minutes.
| Name | Required | Description | Default |
|---|---|---|---|
| course_id | Yes | Numeric course id from search-courses. Example: 1581710. A numeric string such as "1581710" is accepted. |
Output Schema
| Name | Required | Description |
|---|---|---|
| content | Yes | Published syllabus text for this course. |
| course_id | Yes | Course id whose published syllabus was loaded. |
TDQS
A3.9/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by disclosing that a missing generated outline produces an error and should be retried in a few minutes.
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 description is two tightly written sentences with no wasted language. The core return behavior is front-loaded, followed by the important failure/retry condition.
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?
Given the simple one-parameter schema, rich annotations, and existence of an output schema, the description is complete enough for correct invocation. It covers the key behavioral edge case of a not-yet-generated syllabus and the appropriate retry response.
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 description coverage is 100%, and the course_id parameter is already fully documented in the schema, including its source from search-courses and accepted numeric-string form. The description does not add parameter-specific meaning beyond that baseline.
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 states a specific verb and resource: it returns Studocu's generated course outline as markdown. The purpose is unambiguous, though it does not explicitly differentiate this tool from nearby siblings such as get-course-mastery.
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 the tool name and description, and the retry behavior is explained for the case where no outline exists yet. However, the description does not say when to choose this versus alternatives or what prerequisites are required beyond the course_id schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get-project-stateStudocu Project StateARead-onlyIdempotentInspect
List the project sources and creations inside one or more projects. A creation may include external_id (a quiz id or mock-exam id) to match a request-creation result that is still being saved.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | 1 to 20 project ids from get-context or create-project. Example: ["11111111-1111-4111-8111-111111111111"]. Projects you cannot access are left out. |
Output Schema
| Name | Required | Description |
|---|---|---|
| projects | Yes |
TDQS
A3.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the read-only, idempotent, non-destructive profile, so the bar is lower. The description still adds real value by disclosing that creations may carry external_id to match a request-creation result 'still being saved' — i.e. eventual consistency and possible partial visibility, which the annotations do not convey.
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 sentences with zero waste; the core listing behavior is stated first and the external_id nuance follows. Nothing is repeated from the schema or annotations.
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 an output schema present, return values need no explanation, and annotations cover the safety profile; the remaining gap is that the relationship to get-context (the stated source of the ids) is only implied by the schema, not stated in the description.
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 parameter is fully documented with bounds, an example, and the note that inaccessible projects are omitted. The description only echoes 'one or more projects', so the schema does the heavy lifting — baseline 3.
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?
Names a specific verb (List) and resource (project sources and creations) scoped to one or more projects, so an agent knows exactly what it returns. It does not, however, differentiate itself from siblings like get-context or read-artifact, so the agent must infer the boundary.
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 only implied: you call it to inspect project state. The second sentence hints at a polling/matching workflow against request-creation, but never states when to call this tool versus get-context or when to re-call after request-creation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
read-artifactRead Studocu ArtifactARead-onlyIdempotentInspect
Read a project source or creation by its studocu:// id (from get-project-state, add-document-sources, write-artifact, or request-creation). File and image sources also return the image when a viewable copy, or an original upload under 5 MB, exists.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Token from a previous read when the result said there is more, for long content. Omit on the first read. Pass it back unchanged with the same artifact_id. | |
| artifact_id | Yes | Id shaped like studocu://project/{project_id}/{kind}/{uuid}. kind is source (a project source) or creation (a quiz, mock exam, note, flashcard set, or lesson). Example: studocu://project/11111111-1111-4111-8111-111111111111/source/22222222-2222-4222-8222-222222222222. |
Output Schema
| Name | Required | Description |
|---|---|---|
| details | Yes | |
| projectId | Yes | |
| artifactId | Yes | |
| continuations | No |
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only/idempotent/non-destructive, so the bar is lower, and the description still adds a real behavioral trait: file and image sources return an image only when a viewable copy or an original upload under 5 MB exists. It does not disclose that long content is truncated with a cursor, though the schema carries that.
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 sentences with zero filler; the core read action and id provenance come first, and the conditional image behavior is a tight subordinate clause.
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?
An output schema exists so return values needn't be described, and the id/pagination mechanics are fully in the schema. The description covers the id source and the image-return condition, leaving only pagination behavior unmentioned in prose.
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 description coverage is 100%, so both artifact_id and cursor are already fully documented, including the id shape and the cursor round-trip rule. The description only adds provenance for ids, so the baseline 3 applies.
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?
States a specific verb+resource ("Read a project source or creation") and scopes it to the studocu:// id form, with the originating tools named. It does not explicitly differentiate itself from the sibling read-detached-document, which an agent could confuse it with when deciding what to read.
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 tells the agent exactly where a valid artifact_id comes from (get-project-state, add-document-sources, write-artifact, request-creation), which is the practical precondition for calling it. There are no explicit exclusions or pointers to alternative read tools, 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.
read-detached-documentRead Studocu DocumentARead-onlyIdempotentInspect
Read the text of a Studocu document by its search-documents id, without adding it to a project.
| Name | Required | Description | Default |
|---|---|---|---|
| document_id | Yes | Positive integer id from search-documents (documents[].id). Example: 17. |
Output Schema
| Name | Required | Description |
|---|---|---|
| content | Yes | The raw full text content of the Studocu document. |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context by clarifying that the operation does not add the document to a project, though it does not discuss return content or limitations.
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 description is a single efficient sentence with the key action and scope front-loaded. It contains no repetitive or wasted text.
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 a rich output schema, full parameter documentation, and annotations covering safety and idempotency, the description provides enough context for an agent to invoke the tool correctly. The detached/project-free behavior is explicitly stated.
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 description coverage is 100%, and the single parameter already documents its origin and format ("Positive integer id from search-documents... Example: 17"). The description reinforces the id provenance but adds little beyond the 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 states a specific verb and resource: "Read the text of a Studocu document." It also identifies the id source ("search-documents id") and a key scope distinction ("without adding it to a project"), which helps separate it from project-oriented siblings.
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 description gives clear context: use a search-documents id and read the document detached from a project. It does not explicitly name the alternative read/search tools or state when not to use it, so it falls short of full when/when-not/alternative guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
read-memoryRead Studocu Agent MemoryBRead-onlyIdempotentInspect
Read memories saved for this signed-in learner: one per scope and kind.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Return only this kind. Example: "study_preference". Omit to return every saved memory in the chosen scope. | |
| scope | No | Which memories to read: global (learner-wide), project (one project), or both. If omitted, the scope is both when project_id is a UUID, otherwise global. | |
| project_id | No | UUID of the project, or null. Example: 11111111-1111-4111-8111-111111111111. Required when scope is project or both. Omit or null for learner-wide memories. Ignored when scope is global. |
Output Schema
| Name | Required | Description |
|---|---|---|
| memories | Yes | Durable memory documents for the authenticated user. |
TDQS
B3.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful bits beyond that: the memories are scoped to the signed-in learner (auth context) and at most one memory exists per scope/kind combination. It does not describe return shape, but an output schema exists.
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?
A single front-loaded sentence with no filler. It is efficient, though at this length the terseness borders on under-specification given the available scope/kind dimensions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With rich annotations, full schema coverage and an output schema, the description only needs to add selection guidance and it largely doesn't. An agent can call the tool correctly from the schema alone, but the description contributes little beyond confirming it is a scoped read.
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 description coverage is 100% and the schema itself documents kind, scope and project_id including the default-resolution rule and examples. The description adds only the cardinality note ('one per scope and kind'), which is a marginal supplement rather than new parameter semantics.
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?
States a specific verb (read) and resource (memories saved for this signed-in learner), plus a cardinality constraint (one per scope and kind). It is clearly distinguishable from write-memory and delete-memory by name and verb, though it never explicitly names those siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No statement of when to use this tool versus alternatives such as get-context or get-project-state, and no exclusions or prerequisites. The only usage signal is the implicit 'signed-in learner' scoping, which is inferred rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
request-creationGenerate Quiz or Mock ExamAInspect
Ask Studocu to generate a quiz or mock exam from 1 to 10 project sources. Can take about 3 minutes. If status is creating or outcome_unknown, check get-project-state before calling again.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | What to generate: quiz or mockExam. | |
| project_id | Yes | UUID of the project that owns the project sources. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context. | |
| instruction | No | Optional hint, 1-6000 characters. Example: "focus on chapter 3". Omit for a general quiz or mock exam. | |
| artifact_ids | Yes | 1 to 10 different project source ids to generate from. Each id looks like studocu://project/{project_id}/source/{uuid} and must belong to project_id. Get them from add-document-sources or get-project-state. Do not pass creation ids. | |
| idempotency_key | No | Optional retry key, 1-256 characters. Send the same key when you retry the same request. A different request body with a used key is rejected. Omit to let Studocu derive a key from the request; identical retries still count as the same request. |
Output Schema
| Name | Required | Description |
|---|---|---|
| type | Yes | |
| status | Yes | created: saved, with artifact_id and external_id. creating: generation finished but the new creation is not linked yet; match external_id on get-project-state. outcome_unknown: the call timed out or a duplicate is still running; check get-project-state and do not send a new retry key. Failures come back as errors, not as a status. |
| artifact_id | No | Agent OS artifact ID of the new creation. Present when status is created. |
| external_id | No | Quiz id or mock-exam id. Present when status is created or creating. Match it on get-project-state. Omitted when the call times out. |
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the write/safety profile is already known. The description adds genuinely non-structured behavior: the call takes about 3 minutes and can return a creating or outcome_unknown status, both of which change how the agent should sequence its next call. It does not explain what the returned creation id is used for or what happens on failure.
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?
Three short sentences, each carrying distinct information: what is generated, expected latency, and the retry/status protocol. The most decision-relevant content is front-loaded and nothing is repeated from the schema unnecessarily.
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?
An output schema exists, so return values need no explanation, and the description covers the two things an agent would otherwise get wrong: the long latency and the status-check-before-retry loop. It leaves unstated whether the call is asynchronous (returning a creation id) and how the derived idempotency key interacts with the declared idempotentHint=false, a minor but real gap for a creation tool.
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 description coverage is 100%, so every parameter is already documented with examples and constraints. The description only restates the artifact_ids bound ('1 to 10 project sources') and adds no format or selection guidance beyond the schema. Baseline 3 applies when the schema does the heavy lifting.
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?
States a specific verb and resource — generate a quiz or mock exam — plus the scope constraint of 1 to 10 project sources. An agent can identify the tool's job immediately. It does not name a sibling it could be confused with, but no sibling in the list is a competing generator, so differentiation is implicit rather than explicit.
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 a concrete re-entry rule: if status is creating or outcome_unknown, check get-project-state before calling again, which directly names the alternative tool and the condition that selects it. It stops short of stating prerequisites (e.g., sources must be added first) or when not to use the tool at all.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search-coursesSearch CoursesARead-onlyIdempotentInspect
Find a course on Studocu by name or code, to get its course_id for search-documents, get-course-syllabus, or get-course-mastery. Pass institution_id from search-institutions when you know the school. Show the user the name, code, and school, not the id. If several results are plausible, ask the user to pick.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many courses to return. Integer from 1 to 10. Default 3. | |
| query | Yes | Course name or code, 1-200 characters after trimming. Example: "ECON101" or "Introduction to Psychology". | |
| institution_id | No | Numeric school id from search-institutions (the id field). Example: 42. Omit to search every school. Prefer setting it when you already know the school. |
Output Schema
| Name | Required | Description |
|---|---|---|
| courses | Yes |
TDQS
A4.5/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, so the safety profile is covered. The description adds genuine behavioral context beyond that: the disambiguation rule for ambiguous result sets and the presentation rule to surface name/code/school instead of ids. It does not discuss result-set size behavior, but the schema's limit/default covers that.
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?
Four short, front-loaded sentences with no filler: purpose first, then parameter provenance, then user-facing output rule, then disambiguation rule. Every sentence carries an actionable instruction.
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 an output schema present, the description needn't explain return shapes, and it instead spends its budget on the things structured fields can't express: cross-tool provenance for institution_id, downstream id usage, and ambiguity handling. Nothing needed to call this correctly is missing.
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%, so query, limit, and institution_id are all documented in the schema itself, including provenance ('from search-institutions'). The description restates the institution_id provenance and the name-or-code nature of query, which is mildly reinforcing but not additive. Baseline 3 applies when the schema does the heavy lifting.
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 ('Find a course on Studocu by name or code') and immediately distinguishes itself from sibling search tools by naming the downstream consumers (search-documents, get-course-syllabus, get-course-mastery). An agent can tell exactly what this returns and why it exists.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit routing guidance: use institution_id from search-institutions when the school is known, show name/code/school to the user rather than the id, and ask the user to pick when multiple results are plausible. These are concrete when-to-do-what rules rather than implied usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search-documentsDocument SearchARead-onlyIdempotentInspect
Find Studocu documents such as lecture notes and summaries. Pass topic keywords as query. Prefer numeric course_id from search-courses; it overrides course and institution. Results with match_type: semantic are closest matches, not exact keyword hits, and may be only loosely related.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many Studocu documents to return. Integer from 1 to 50. Default 10. | |
| query | Yes | Topic keywords only. Example: "supply and demand" or "microeconomics midterm 2025". Do not put a course name, course id, or school name here. Use institution, course, and course_id for those. | |
| course | No | Course name or code. Example: "Economics" or "ECON101". Use this when you do not have course_id. Do not put a numeric id here. Optional extra when you already have course_id. Omit if unknown. | |
| course_id | No | Numeric course id from search-courses (the course_id field). Example: 1581710. Prefer this: it pins the course and overrides the course name or code. Omit if you only have a name or code. | |
| institution | No | School name only. Example: "University of Amsterdam". Not an id. This tool has no institution_id. Use the name from the user or from search-institutions. Omit if unknown. If course_id is also set, course_id wins and the result school is that course's school, not this name. | |
| use_no_course_as_fallback | No | Only used with course_id. When true and that course has no matching Studocu documents, search again without the course, so results may come from other courses. Check each result's course_id. Default false. Omit for false. |
Output Schema
| Name | Required | Description |
|---|---|---|
| documents | Yes |
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: semantic matches are not exact keyword hits and may be only loosely relevant, and course_id silently overrides other scoping fields.
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?
Three tight sentences, front-loaded with the core action, then the query convention, then the scoping precedence rule. Every sentence carries actionable information and there is no filler.
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 six parameters, full schema coverage, an output schema, and complete annotations, the description needs only to cover routing and result-interpretation caveats, which it does. The only minor gap is that use_no_course_as_fallback's purpose is left entirely to the schema.
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 description coverage is 100%, so each parameter including use_no_course_as_fallback and the query restrictions is already documented in the schema. The description reinforces the course_id override rule but adds no parameter meaning that isn't already present in structured fields, making 3 the appropriate baseline.
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?
States a specific verb and resource ("Find Studocu documents such as lecture notes and summaries") and names search-courses as the source for course_id, which clarifies the workflow relationship. It doesn't explicitly distinguish itself from read-only siblings like read-detached-document or read-artifact, so differentiation is only partial.
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?
"Prefer numeric course_id from search-courses; it overrides course and institution" gives concrete precedence guidance an agent can act on. It also warns that semantic match_type results may be loosely related, which sets expectations about result quality, though there is no explicit statement of when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search-institutionsSearch InstitutionsARead-onlyIdempotentInspect
Find a school (university or high school) on Studocu by name, to get its id for search-courses. Show the user the name, type, and country, not the id. If several results are plausible, ask the user to pick.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Optional filter: UNIVERSITY or HIGH_SCHOOL. Omit to search both. | |
| limit | No | How many schools to return. Integer from 1 to 10. Default 3. | |
| query | Yes | School name to search, 1-200 characters after trimming. Example: "University of Amsterdam". |
Output Schema
| Name | Required | Description |
|---|---|---|
| institutions | Yes |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, so the description focuses on value-add behavior: presentation rules (show name, type, country, not the id) and the ask-the-user fallback for ambiguous results. It does not cover result volume or empty-result handling, keeping it short of 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.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, each doing distinct work: purpose, downstream chaining, presentation, and ambiguity handling. The purpose is front-loaded with no filler.
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 small read-only lookup with an output schema and full annotation coverage, the description supplies everything an agent needs: what it finds, why it is called, what to surface to the user, and what to do with multiple plausible matches.
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 each parameter (query, type, limit) is fully documented with constraints and examples, so the description need not repeat them. The description's mention of "type" refers to a result field rather than the type filter, adding no parameter meaning.
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 ("Find a school (university or high school) on Studocu by name") and immediately distinguishes it from the sibling search-courses by naming it as the downstream consumer of the returned id.
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?
Explicitly frames the use case as "to get its id for search-courses" and gives a disambiguation rule ("If several results are plausible, ask the user to pick"). It lacks an explicit when-not-to-use statement, but the routing to search-courses supplies clear context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
update-projectUpdate Studocu ProjectAIdempotentInspect
Change the name, icon, or linked course of an existing project. Pass course_id null to unlink the course.
| Name | Required | Description | Default |
|---|---|---|---|
| emoji | No | New icon text, usually an emoji. Example: "📚". Omit to leave it unchanged. | |
| title | No | New name, 1-255 characters, with at least one non-space character. Example: "Biology midterm". Omit to leave the name unchanged. | |
| course_id | No | Positive integer course id from search-courses, or null to unlink the course. Example: 1581710. Omit to leave the link unchanged. | |
| project_id | Yes | UUID of the project to change. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context. |
Output Schema
| Name | Required | Description |
|---|---|---|
| emoji | Yes | |
| title | Yes | Agent-displayable project title. Null Alpha names become "Untitled project". |
| course_id | Yes | |
| is_mobile | Yes | |
| project_id | Yes | UUID string in 8-4-4-4-12 hexadecimal form. Example: 11111111-1111-4111-8111-111111111111. |
| institution_id | Yes |
TDQS
A3.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare idempotentHint=true and destructiveHint=false, so the description does not need to argue safety; what it does add is genuinely new behavior — that passing course_id null unlinks the course, which is a removal-ish semantic an agent would otherwise not anticipate. It omits that omitting a field leaves it unchanged (that lives only in the schema property descriptions).
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, with the capability stated first and the one non-obvious parameter behavior second. Every clause carries information.
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 an output schema, full annotation coverage, and 100% schema descriptions, the description need only orient the agent, which it does. The main gap is that it never states the 'at least one field must be provided' rule that the schema enforces via anyOf and minProperties.
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 description coverage is 100%, and each parameter already documents omit-to-leave-unchanged and null-to-unlink, so the description largely restates schema content. Baseline 3 applies; no extra syntax, id provenance, or partial-update rules are added beyond what the schema says.
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?
States a specific verb ('Change') plus the resource ('an existing project') and enumerates the three mutable fields (name, icon, linked course), so an agent can tell it is the mutation counterpart to create-project. It does not explicitly name get-project-state or create-project, but the 'existing project' framing makes the distinction inferable.
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: it operates on an existing project and supports partial updates, and the null-unlink carve-out hints at how to remove a link. There is no explicit when-to-use vs. create-project guidance and no statement of the precondition that at least one optional field must be supplied (the schema's anyOf/minProperties), so the agent must open the schema to learn that.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
write-artifactSave Study Item to ProjectAInspect
Save a quiz, mock exam, note, or flashcard set you have already written into a project. To have Studocu generate a quiz or mock exam instead, use request-creation.
| Name | Required | Description | Default |
|---|---|---|---|
| artifact | Yes | The creation to save. type is quiz, mockExam, note, or flashcard. Each type has its own content shape. kind must be creation. | |
| project_id | Yes | UUID of the project that will own the creation. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context. |
Output Schema
| Name | Required | Description |
|---|---|---|
| kind | Yes | Artifact kind returned by the write operation. |
| type | Yes | Creation type that was written. |
| title | Yes | Human-readable title of the created artifact. |
| status | Yes | Stable write status for successful creation writes. |
| projectId | Yes | UUID of the Studocu project that owns the created artifact. |
| artifactId | Yes | Canonical Studocu artifact URI for the created creation. |
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the safety profile is covered. The description usefully signals the pre-condition that the artifact must already be authored ('you have already written'), but says nothing about what happens on repeated saves (idempotentHint=false leaves duplicate-vs-overwrite unclear) or validation/error behavior.
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 sentences, zero waste, with the what front-loaded and the routing alternative second. Nothing could be removed without losing routing value.
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 a very detailed input schema and an output schema present, the description only needs to convey purpose and routing, which it does. It is slightly thin on the write semantics (duplication on re-save, relationship to project sources) that the agent cannot infer from structured fields alone.
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 description coverage is 100% and the artifact oneOf fully documents each shape, so the schema does the heavy lifting. The description only echoes the four artifact types already enumerated in the schema; it adds no new parameter meaning such as project_id sourcing or artifact discrimination rules.
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 (save) and a precise resource (quiz, mock exam, note, or flashcard set) scoped to a project, and explicitly names the sibling it is not (request-creation). An agent can tell it apart from request-creation without opening either schema.
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?
Names the alternative tool and the condition that selects it ('To have Studocu generate ... instead, use request-creation'), which is the main routing decision for this tool. It stops short of covering other relevant cases, e.g. reading back existing artifacts with read-artifact or the fact that project sources cannot be written here (that only appears in the schema).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
write-memoryWrite Studocu Agent MemoryADestructiveIdempotentInspect
Save one memory (a preference or project fact) for this learner. Writing the same kind again replaces it.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | Kind for this memory. At least 1 character. Example: "study_preference" or "project_learning_context". Writing the same kind again replaces the previous memory. | |
| value | Yes | JSON object to store. Usual shape: { "content": "the memory text" }. Other keys are allowed. | |
| project_id | No | UUID of the project this memory belongs to, or null. Example: 11111111-1111-4111-8111-111111111111. Omit or null to store a learner-wide memory. |
Output Schema
| Name | Required | Description |
|---|---|---|
| kind | Yes | Memory kind that was written. |
| value | Yes | Stored memory document. |
| userId | Yes | Owner of the memory document. |
| createdAt | Yes | Creation timestamp of the row. |
| projectId | Yes | Owning project UUID, or null for global memory. |
| updatedAt | Yes | Last write timestamp of the row. |
TDQS
A3.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true, but they don't say what is destroyed. The description fills that gap precisely: only the memory of the same kind is replaced, not the whole store. It omits rate limits or auth requirements, but for this tool the key hazard is fully disclosed.
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 overwrite semantics are front-loaded in the second sentence where an agent will see them before writing.
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?
Output schema exists and the input schema is fully documented, so the description only needs to carry behavior. It does so for the replacement semantics; the only minor gap is not restating that omitting project_id yields a learner-wide memory, which the schema already covers.
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 description coverage is 100%, so kind, value, and project_id are already well documented, including the replacement rule and the usual {content: ...} shape. The description reinforces that the payload is a preference or project fact but adds no syntax or format detail beyond the schema; baseline 3 is appropriate.
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?
States a specific verb ("Save") and resource ("one memory") with the content scoped ("a preference or project fact") and the owner ("this learner"). It is clearly distinct from read-memory, delete-memory, and write-artifact, though it never names those siblings explicitly.
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?
The parenthetical "a preference or project fact" implies the appropriate content, and the replacement rule signals the overwrite consequence. However, there is no explicit when-to-use vs. when-not guidance and no reference to alternatives such as write-artifact or create-project.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
17 tool updates
- Changed
add-document-sources2 fields changed- changed
Input schema / properties / document_ids / descriptionPrevious value: -"One to ten unique Studocu document IDs returned by search-documents."New value: +"1 to 10 different positive integer Studocu document ids from search-documents (documents[].id). Example: [17, 42]." - changed
Input schema / properties / project_id / descriptionPrevious value: -"UUID of the Studocu project that will receive the document sources."New value: +"UUID of the project that should receive the Studocu documents. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context."
- Changed
create-project4 fields changed- added
Input schema / properties / course_id / descriptionAdded value: +"Positive integer course id from search-courses. Example: 1581710. The course is checked before the project is created; an unknown id creates nothing. Omit to leave the project unlinked." - added
Input schema / properties / emoji / descriptionAdded value: +"Icon text, usually an emoji. Example: \"📚\". Omit to leave the icon unset." - added
Input schema / properties / title / descriptionAdded value: +"Name, 1-255 characters, with at least one non-space character. Example: \"Biology midterm\". Omit to create the project without a name; the returned title is then \"Untitled project\"." - changed
Output schema / properties / project_id / descriptionPrevious value: -"NOTE: These shared primitives are copied from the AI API spec and owned\nlocally by Agent OS to keep this contract decoupled."New value: +"UUID string in 8-4-4-4-12 hexadecimal form. Example: 11111111-1111-4111-8111-111111111111."
- Changed
delete-memory2 fields changed- changed
Input schema / properties / kind / descriptionPrevious value: -"Memory kind to delete, e.g. study_preference or project_learning_context."New value: +"Kind of the memory to delete. Example: \"study_preference\" or \"project_learning_context\"." - changed
Input schema / properties / project_id / descriptionPrevious value: -"Project UUID for project-local memory; null or omitted deletes global (user-level) memory."New value: +"UUID of the project memory to delete, or null. Example: 11111111-1111-4111-8111-111111111111. Omit or null to delete a learner-wide memory."
- Changed
get-context4 fields changed- changed
Input schema / properties / active_only / descriptionPrevious value: -"Limit the manifest to active context."New value: +"Optional true or false. It is echoed on the response and does not change which courses or projects are returned. Omit it." - changed
Input schema / properties / course_id / descriptionPrevious value: -"Narrow context to a single followed course and its projects."New value: +"Return only this course and its projects. Numeric id or the same id as text. Example: 1581710 or \"1581710\". Omit to include every followed course." - changed
Input schema / properties / project_id / descriptionPrevious value: -"Narrow context to a single project by id."New value: +"Return only this project. Example: \"11111111-1111-4111-8111-111111111111\". From an earlier get-context or create-project result. Omit to include the learner's projects." - changed
Input schema / properties / recent_only / descriptionPrevious value: -"Limit the manifest to recently active context."New value: +"Optional true or false. It is echoed on the response and does not change which courses or projects are returned. Omit it."
- Changed
get-course-mastery2 fields changed- changed
Input schema / properties / course_id / descriptionPrevious value: -"Course id to load practised-topic Infinite Practice mastery for."New value: +"Numeric course id from search-courses or get-context. Example: 1581710. A numeric string such as \"1581710\" is accepted." - changed
Output schema / properties / topic_masteries / descriptionPrevious value: -"Practised topics only. Empty means this course was loaded and the learner has no IP attempts yet."New value: +"Topics the learner has already practised. Empty means this course was loaded and they have not practised yet."
- Changed
get-course-syllabus1 field changed- changed
Input schema / properties / course_id / descriptionPrevious value: -"Studocu course id whose published syllabus should be loaded."New value: +"Numeric course id from search-courses. Example: 1581710. A numeric string such as \"1581710\" is accepted."
- Changed
get-project-state1 field changed- changed
Input schema / properties / ids / descriptionPrevious value: -"The project ids to load sources and creations (project state) for. Only projects you can access are returned."New value: +"1 to 20 project ids from get-context or create-project. Example: [\"11111111-1111-4111-8111-111111111111\"]. Projects you cannot access are left out."
- Changed
read-artifact3 fields changed- changed
Input schema / properties / artifact_id / descriptionPrevious value: -"Artifact URI in the form studocu://project/{project_id}/{kind}/{uuid}."New value: +"Id shaped like studocu://project/{project_id}/{kind}/{uuid}. kind is source (a project source) or creation (a quiz, mock exam, note, flashcard set, or lesson). Example: studocu://project/11111111-1111-4111-8111-111111111111/source/22222222-2222-4222-8222-222222222222." - changed
Input schema / properties / cursor / descriptionPrevious value: -"Opaque continuation cursor returned by a previous read."New value: +"Token from a previous read when the result said there is more, for long content. Omit on the first read. Pass it back unchanged with the same artifact_id." - changed
Output schema / properties / details / properties / id / descriptionPrevious value: -"NOTE: These shared primitives are copied from the AI API spec and owned\nlocally by Agent OS to keep this contract decoupled."New value: +"UUID string in 8-4-4-4-12 hexadecimal form. Example: 11111111-1111-4111-8111-111111111111."
- Changed
read-detached-document1 field changed- changed
Input schema / properties / document_id / descriptionPrevious value: -"Studocu document ID to read without creating a project source."New value: +"Positive integer id from search-documents (documents[].id). Example: 17."
- Changed
read-memory3 fields changed- changed
Input schema / properties / kind / descriptionPrevious value: -"Narrow the result to a single memory kind."New value: +"Return only this kind. Example: \"study_preference\". Omit to return every saved memory in the chosen scope." - changed
Input schema / properties / project_id / descriptionPrevious value: -"Project UUID for project-scoped memory; null or omitted reads global (user-level) memory. Required when scope is project or both."New value: +"UUID of the project, or null. Example: 11111111-1111-4111-8111-111111111111. Required when scope is project or both. Omit or null for learner-wide memories. Ignored when scope is global." - changed
Input schema / properties / scope / descriptionPrevious value: -"Memory scope to read: global, project, or both. Defaults to global unless project_id is set."New value: +"Which memories to read: global (learner-wide), project (one project), or both. If omitted, the scope is both when project_id is a UUID, otherwise global."
- Changed
request-creation7 fields changed- changed
Input schema / properties / artifact_ids / descriptionPrevious value: -"One to ten unique source artifact IDs (studocu://project/{project_id}/source/{uuid}) to generate from."New value: +"1 to 10 different project source ids to generate from. Each id looks like studocu://project/{project_id}/source/{uuid} and must belong to project_id. Get them from add-document-sources or get-project-state. Do not pass creation ids." - changed
Input schema / properties / idempotency_key / descriptionPrevious value: -"Optional retry key. Agent OS always sends Idempotency-Key to Alpha (this value, or a fingerprint of project/type/sources/instruction). Reuse with a different body is rejected."New value: +"Optional retry key, 1-256 characters. Send the same key when you retry the same request. A different request body with a used key is rejected. Omit to let Studocu derive a key from the request; identical retries still count as the same request." - changed
Input schema / properties / instruction / descriptionPrevious value: -"Optional free-text hint for the generating agent (e.g. \"focus on chapter 3\")."New value: +"Optional hint, 1-6000 characters. Example: \"focus on chapter 3\". Omit for a general quiz or mock exam." - changed
Input schema / properties / project_id / descriptionPrevious value: -"UUID of the Studocu project that will own the new creation."New value: +"UUID of the project that owns the project sources. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context." - changed
Input schema / properties / type / descriptionPrevious value: -"The kind of creation to generate: quiz or mockExam."New value: +"What to generate: quiz or mockExam." - changed
Output schema / properties / external_id / descriptionPrevious value: -"Kind-specific downstream id (quizId or mockExamId). Present on created and creating; match the same field on get-project-state creation rows. Omitted on timeout."New value: +"Quiz id or mock-exam id. Present when status is created or creating. Match it on get-project-state. Omitted when the call times out." - changed
Output schema / properties / status / descriptionPrevious value: -"created: persisted and linked (artifact_id and external_id). creating: generation finished but Alpha identity is not yet visible (external_id matches get-project-state creation rows). outcome_unknown: client timeout or an in-flight duplicate (check get-project-state; do not mint a new key). Terminal failures use MCP isError, not a status value."New value: +"created: saved, with artifact_id and external_id. creating: generation finished but the new creation is not linked yet; match external_id on get-project-state. outcome_unknown: the call timed out or a duplicate is still running; check get-project-state and do not send a new retry key. Failures come back as errors, not as a status."
- Changed
search-courses3 fields changed- added
Input schema / properties / institution_id / descriptionAdded value: +"Numeric school id from search-institutions (the id field). Example: 42. Omit to search every school. Prefer setting it when you already know the school." - added
Input schema / properties / limit / descriptionAdded value: +"How many courses to return. Integer from 1 to 10. Default 3." - added
Input schema / properties / query / descriptionAdded value: +"Course name or code, 1-200 characters after trimming. Example: \"ECON101\" or \"Introduction to Psychology\"."
- Changed
search-documents6 fields changed- changed
Input schema / properties / course / descriptionPrevious value: -"Course name or code only, e.g. \"Economics\" or \"ECON101\". Use when you do not have `course_id`. Never put a numeric id here. Optional extra if you also have `course_id`. Omit entirely if unknown."New value: +"Course name or code. Example: \"Economics\" or \"ECON101\". Use this when you do not have course_id. Do not put a numeric id here. Optional extra when you already have course_id. Omit if unknown." - changed
Input schema / properties / course_id / descriptionPrevious value: -"Numeric Studocu course ID from search-courses `course_id`. Prefer this: it pins the course and overrules `course` name/code. Omit if you only have a name/code."New value: +"Numeric course id from search-courses (the course_id field). Example: 1581710. Prefer this: it pins the course and overrides the course name or code. Omit if you only have a name or code." - changed
Input schema / properties / institution / descriptionPrevious value: -"Institution display name only, e.g. \"University of Amsterdam\". Not an id — this tool has no `institution_id`. Infer it from the user message or conversation context when available; omit entirely if unknown. If `course_id` is also set, `course_id` wins; result institution is that course's university, not this name."New value: +"School name only. Example: \"University of Amsterdam\". Not an id. This tool has no institution_id. Use the name from the user or from search-institutions. Omit if unknown. If course_id is also set, course_id wins and the result school is that course's school, not this name." - changed
Input schema / properties / limit / descriptionPrevious value: -"Number of results to return (1-50, default: 10)."New value: +"How many Studocu documents to return. Integer from 1 to 50. Default 10." - changed
Input schema / properties / query / descriptionPrevious value: -"Topic/keywords only (e.g. \"supply and demand\", \"microeconomics midterm 2025\"). Never put course name, course id, or institution name here — use `institution`, `course`, and `course_id` instead."New value: +"Topic keywords only. Example: \"supply and demand\" or \"microeconomics midterm 2025\". Do not put a course name, course id, or school name here. Use institution, course, and course_id for those." - changed
Input schema / properties / use_no_course_as_fallback / descriptionPrevious value: -"Only used with `course_id`. When true and that course has no matching documents, search again without the course, so results may come from other courses; check each result's `course_id`. Default false."New value: +"Only used with course_id. When true and that course has no matching Studocu documents, search again without the course, so results may come from other courses. Check each result's course_id. Default false. Omit for false."
- Changed
search-institutions3 fields changed- added
Input schema / properties / limit / descriptionAdded value: +"How many schools to return. Integer from 1 to 10. Default 3." - added
Input schema / properties / query / descriptionAdded value: +"School name to search, 1-200 characters after trimming. Example: \"University of Amsterdam\"." - added
Input schema / properties / type / descriptionAdded value: +"Optional filter: UNIVERSITY or HIGH_SCHOOL. Omit to search both."
- Changed
update-project5 fields changed- added
Input schema / properties / course_id / descriptionAdded value: +"Positive integer course id from search-courses, or null to unlink the course. Example: 1581710. Omit to leave the link unchanged." - added
Input schema / properties / emoji / descriptionAdded value: +"New icon text, usually an emoji. Example: \"📚\". Omit to leave it unchanged." - changed
Input schema / properties / project_id / descriptionPrevious value: -"NOTE: These shared primitives are copied from the AI API spec and owned\nlocally by Agent OS to keep this contract decoupled."New value: +"UUID of the project to change. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context." - added
Input schema / properties / title / descriptionAdded value: +"New name, 1-255 characters, with at least one non-space character. Example: \"Biology midterm\". Omit to leave the name unchanged." - changed
Output schema / properties / project_id / descriptionPrevious value: -"NOTE: These shared primitives are copied from the AI API spec and owned\nlocally by Agent OS to keep this contract decoupled."New value: +"UUID string in 8-4-4-4-12 hexadecimal form. Example: 11111111-1111-4111-8111-111111111111."
- Changed
write-artifact3 fields changed- changed
Input schema / properties / artifact / descriptionPrevious value: -"The artifact to create. Pick type; each type defines its own content shape."New value: +"The creation to save. type is quiz, mockExam, note, or flashcard. Each type has its own content shape. kind must be creation." - changed
Input schema / properties / artifact / oneOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "content": { - "additionalProperties": false, - "description": "Quiz content.", - "properties": { - "course_id": { - "exclusiveMinimum": 0, - "maximum": 9007199254740991, - "type": "integer" - }, - "questions": { - "items": { - "additionalProperties": false, - "properties": { - "answers": { - "items": { - "additionalProperties": false, - "properties": { - "answer": { - "description": "Answer option text.", - "minLength": 1, - "type": "string" - }, - "is_correct": { - "description": "True for the correct option or options.", - "type": "boolean" - } - }, - "required": [ - "answer", - "is_correct" - ], - "type": "object" - }, - "minItems": 2, - "type": "array" - }, - "difficulty": { - "enum": [ - "EASY", - "MEDIUM", - "HARD" - ], - "type": "string" - }, - "explanation": { - "description": "Required explanation for the correct answer (Core quiz API requires it, max 255 characters).", - "maxLength": 255, - "minLength": 1, - "type": "string" - }, - "question": { - "description": "Question prompt shown to the learner.", - "minLength": 1, - "type": "string" - } - }, - "required": [ - "question", - "answers", - "explanation" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } - }, - "required": [ - "questions" - ], - "type": "object" - }, - "description": { - "description": "Optional description stored on the creation record.", - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "creation", - "description": "Artifact kind. Only creation is writable in this MVP.", - "type": "string" - }, - "title": { - "description": "Human-readable quiz title (Core Labs API requires 20-255 characters).", - "maxLength": 255, - "minLength": 20, - "type": "string" - }, - "type": { - "const": "quiz", - "type": "string" - } - }, - "required": [ - "kind", - "title", - "type", - "content" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "content": { - "additionalProperties": false, - "description": "Mock exam content.", - "properties": { - "exam_json": { - "additionalProperties": false, - "properties": { - "content": { - "items": { - "oneOf": [ - { - "additionalProperties": false, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "instructions": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "section", - "type": "string" - }, - "question_type": { - "description": "Frontend-supported KnowledgeTest question type. Use mcq, not multiple_choice.", - "enum": [ - "mcq", - "multi_select", - "true_false", - "fill_in_blank", - "text_answer_short", - "text_answer_long" - ], - "type": "string" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "kind", - "id", - "question_type" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "stimulus", - "type": "string" - }, - "stimulus_markdown": { - "minLength": 1, - "type": "string" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "kind", - "id", - "stimulus_markdown" - ], - "type": "object" - }, - { - "oneOf": [ - { - "additionalProperties": false, - "properties": { - "grading": { - "additionalProperties": false, - "properties": { - "correct_answer": { - "type": "string" - }, - "correct_answer_ids": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "key_points": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "model_answer": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "model_answer" - ], - "type": "object" - }, - "id": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "question", - "type": "string" - }, - "marks": { - "minimum": 0, - "type": "number" - }, - "options": { - "items": { - "additionalProperties": false, - "properties": { - "id": { - "description": "Stable option id.", - "minLength": 1, - "type": "string" - }, - "text": { - "description": "Option text.", - "minLength": 1, - "type": "string" - } - }, - "required": [ - "id", - "text" - ], - "type": "object" - }, - "minItems": 2, - "type": "array" - }, - "question_markdown": { - "minLength": 1, - "type": "string" - }, - "section_id": { - "minLength": 1, - "type": "string" - }, - "stimulus_id_refs": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "topics": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "type": { - "enum": [ - "mcq", - "multi_select", - "true_false" - ], - "type": "string" - } - }, - "required": [ - "kind", - "id", - "section_id", - "type", - "marks", - "question_markdown", - "options" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "blanks": { - "items": { - "additionalProperties": false, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "label": { - "type": "string" - } - }, - "required": [ - "id" - ], - "type": "object" - }, - "type": "array" - }, - "grading": { - "additionalProperties": false, - "properties": { - "correct_answer": { - "type": "string" - }, - "correct_answer_ids": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "key_points": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "model_answer": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "model_answer" - ], - "type": "object" - }, - "id": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "question", - "type": "string" - }, - "marks": { - "minimum": 0, - "type": "number" - }, - "question_markdown": { - "minLength": 1, - "type": "string" - }, - "section_id": { - "minLength": 1, - "type": "string" - }, - "stimulus_id_refs": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "template_markdown": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "topics": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "type": { - "const": "fill_in_blank", - "type": "string" - } - }, - "required": [ - "kind", - "id", - "section_id", - "type", - "marks", - "question_markdown" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "grading": { - "additionalProperties": false, - "properties": { - "correct_answer": { - "type": "string" - }, - "correct_answer_ids": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "key_points": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "model_answer": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "model_answer" - ], - "type": "object" - }, - "id": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "question", - "type": "string" - }, - "marks": { - "minimum": 0, - "type": "number" - }, - "question_markdown": { - "minLength": 1, - "type": "string" - }, - "section_id": { - "minLength": 1, - "type": "string" - }, - "stimulus_id_refs": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "topics": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "type": { - "enum": [ - "text_answer_short", - "text_answer_long" - ], - "type": "string" - } - }, - "required": [ - "kind", - "id", - "section_id", - "type", - "marks", - "question_markdown" - ], - "type": "object" - } - ] - } - ] - }, - "minItems": 1, - "type": "array" - }, - "front_matter": { - "additionalProperties": false, - "properties": { - "instructions_markdown": { - "type": "string" - } - }, - "type": "object" - }, - "schema_version": { - "const": "0.8", - "type": "string" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "schema_version", - "title", - "content" - ], - "type": "object" - } - }, - "required": [ - "exam_json" - ], - "type": "object" - }, - "description": { - "description": "Optional description stored on the creation record.", - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "creation", - "description": "Artifact kind. Only creation is writable in this MVP.", - "type": "string" - }, - "title": { - "description": "Human-readable title for the created artifact.", - "minLength": 1, - "type": "string" - }, - "type": { - "const": "mockExam", - "type": "string" - } - }, - "required": [ - "kind", - "title", - "type", - "content" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "content": { - "additionalProperties": false, - "description": "Note content.", - "properties": { - "html": { - "description": "Complete HTML document for the note body (max 1 MiB UTF-8).", - "minLength": 1, - "type": "string" - } - }, - "required": [ - "html" - ], - "type": "object" - }, - "kind": { - "const": "creation", - "description": "Artifact kind. Only creation is writable in this MVP.", - "type": "string" - }, - "title": { - "description": "Human-readable note title (Alpha creation store max 255 characters).", - "maxLength": 255, - "minLength": 1, - "type": "string" - }, - "type": { - "const": "note", - "type": "string" - } - }, - "required": [ - "kind", - "title", - "type", - "content" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "content": { - "additionalProperties": false, - "description": "Flashcard set content.", - "properties": { - "flashcards_json": { - "additionalProperties": false, - "properties": { - "description": { - "type": "string" - }, - "flashcards": { - "items": { - "additionalProperties": false, - "properties": { - "back": { - "minLength": 1, - "type": "string" - }, - "front": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "front", - "back" - ], - "type": "object" - }, - "maxItems": 200, - "minItems": 1, - "type": "array" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "title", - "description", - "flashcards" - ], - "type": "object" - } - }, - "required": [ - "flashcards_json" - ], - "type": "object" - }, - "description": { - "description": "Optional description stored on the creation record.", - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "creation", - "description": "Artifact kind. Only creation is writable in this MVP.", - "type": "string" - }, - "title": { - "description": "Human-readable title for the created artifact.", - "minLength": 1, - "type": "string" - }, - "type": { - "const": "flashcard", - "type": "string" - } - }, - "required": [ - "kind", - "title", - "type", - "content" - ], - "type": "object" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "content": { + "additionalProperties": false, + "description": "Quiz content.", + "properties": { + "course_id": { + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" + }, + "questions": { + "items": { + "additionalProperties": false, + "properties": { + "answers": { + "items": { + "additionalProperties": false, + "properties": { + "answer": { + "description": "Answer option text.", + "minLength": 1, + "type": "string" + }, + "is_correct": { + "description": "True for the correct option or options.", + "type": "boolean" + } + }, + "required": [ + "answer", + "is_correct" + ], + "type": "object" + }, + "minItems": 2, + "type": "array" + }, + "difficulty": { + "enum": [ + "EASY", + "MEDIUM", + "HARD" + ], + "type": "string" + }, + "explanation": { + "description": "Why the correct answer is right. Required. 1-255 characters.", + "maxLength": 255, + "minLength": 1, + "type": "string" + }, + "question": { + "description": "Question prompt shown to the learner.", + "minLength": 1, + "type": "string" + } + }, + "required": [ + "question", + "answers", + "explanation" + ], + "type": "object" + }, + "minItems": 1, + "type": "array" + } + }, + "required": [ + "questions" + ], + "type": "object" + }, + "description": { + "description": "Optional short description of the creation (quiz, mock exam, or flashcard set). The note type does not have this field.", + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "creation", + "description": "Must be the string creation. A project source cannot be written with this tool.", + "type": "string" + }, + "title": { + "description": "Quiz title shown to the learner. 20-255 characters.", + "maxLength": 255, + "minLength": 20, + "type": "string" + }, + "type": { + "const": "quiz", + "type": "string" + } + }, + "required": [ + "kind", + "title", + "type", + "content" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "content": { + "additionalProperties": false, + "description": "Mock exam content.", + "properties": { + "exam_json": { + "additionalProperties": false, + "properties": { + "content": { + "items": { + "oneOf": [ + { + "additionalProperties": false, + "properties": { + "id": { + "minLength": 1, + "type": "string" + }, + "instructions": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "section", + "type": "string" + }, + "question_type": { + "description": "Question type: mcq, multi_select, true_false, fill_in_blank, text_answer_short, or text_answer_long. Use mcq, not multiple_choice.", + "enum": [ + "mcq", + "multi_select", + "true_false", + "fill_in_blank", + "text_answer_short", + "text_answer_long" + ], + "type": "string" + }, + "title": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "kind", + "id", + "question_type" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "id": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "stimulus", + "type": "string" + }, + "stimulus_markdown": { + "minLength": 1, + "type": "string" + }, + "title": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "kind", + "id", + "stimulus_markdown" + ], + "type": "object" + }, + { + "oneOf": [ + { + "additionalProperties": false, + "properties": { + "grading": { + "additionalProperties": false, + "properties": { + "correct_answer": { + "type": "string" + }, + "correct_answer_ids": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "key_points": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "model_answer": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "model_answer" + ], + "type": "object" + }, + "id": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "question", + "type": "string" + }, + "marks": { + "minimum": 0, + "type": "number" + }, + "options": { + "items": { + "additionalProperties": false, + "properties": { + "id": { + "description": "Stable option id.", + "minLength": 1, + "type": "string" + }, + "text": { + "description": "Option text.", + "minLength": 1, + "type": "string" + } + }, + "required": [ + "id", + "text" + ], + "type": "object" + }, + "minItems": 2, + "type": "array" + }, + "question_markdown": { + "minLength": 1, + "type": "string" + }, + "section_id": { + "minLength": 1, + "type": "string" + }, + "stimulus_id_refs": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "topics": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "type": { + "enum": [ + "mcq", + "multi_select", + "true_false" + ], + "type": "string" + } + }, + "required": [ + "kind", + "id", + "section_id", + "type", + "marks", + "question_markdown", + "options" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "blanks": { + "items": { + "additionalProperties": false, + "properties": { + "id": { + "minLength": 1, + "type": "string" + }, + "label": { + "type": "string" + } + }, + "required": [ + "id" + ], + "type": "object" + }, + "type": "array" + }, + "grading": { + "additionalProperties": false, + "properties": { + "correct_answer": { + "type": "string" + }, + "correct_answer_ids": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "key_points": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "model_answer": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "model_answer" + ], + "type": "object" + }, + "id": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "question", + "type": "string" + }, + "marks": { + "minimum": 0, + "type": "number" + }, + "question_markdown": { + "minLength": 1, + "type": "string" + }, + "section_id": { + "minLength": 1, + "type": "string" + }, + "stimulus_id_refs": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "template_markdown": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "topics": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "type": { + "const": "fill_in_blank", + "type": "string" + } + }, + "required": [ + "kind", + "id", + "section_id", + "type", + "marks", + "question_markdown" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "grading": { + "additionalProperties": false, + "properties": { + "correct_answer": { + "type": "string" + }, + "correct_answer_ids": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "key_points": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "model_answer": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "model_answer" + ], + "type": "object" + }, + "id": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "question", + "type": "string" + }, + "marks": { + "minimum": 0, + "type": "number" + }, + "question_markdown": { + "minLength": 1, + "type": "string" + }, + "section_id": { + "minLength": 1, + "type": "string" + }, + "stimulus_id_refs": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "topics": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "type": { + "enum": [ + "text_answer_short", + "text_answer_long" + ], + "type": "string" + } + }, + "required": [ + "kind", + "id", + "section_id", + "type", + "marks", + "question_markdown" + ], + "type": "object" + } + ] + } + ] + }, + "minItems": 1, + "type": "array" + }, + "front_matter": { + "additionalProperties": false, + "properties": { + "instructions_markdown": { + "type": "string" + } + }, + "type": "object" + }, + "schema_version": { + "const": "0.8", + "type": "string" + }, + "title": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "schema_version", + "title", + "content" + ], + "type": "object" + } + }, + "required": [ + "exam_json" + ], + "type": "object" + }, + "description": { + "description": "Optional short description of the creation (quiz, mock exam, or flashcard set). The note type does not have this field.", + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "creation", + "description": "Must be the string creation. A project source cannot be written with this tool.", + "type": "string" + }, + "title": { + "description": "Title shown to the learner. At least 1 character.", + "minLength": 1, + "type": "string" + }, + "type": { + "const": "mockExam", + "type": "string" + } + }, + "required": [ + "kind", + "title", + "type", + "content" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "content": { + "additionalProperties": false, + "description": "Note content.", + "properties": { + "html": { + "description": "Complete HTML document for the note body (max 1 MiB UTF-8).", + "minLength": 1, + "type": "string" + } + }, + "required": [ + "html" + ], + "type": "object" + }, + "kind": { + "const": "creation", + "description": "Must be the string creation. A project source cannot be written with this tool.", + "type": "string" + }, + "title": { + "description": "Note title. 1-255 characters.", + "maxLength": 255, + "minLength": 1, + "type": "string" + }, + "type": { + "const": "note", + "type": "string" + } + }, + "required": [ + "kind", + "title", + "type", + "content" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "content": { + "additionalProperties": false, + "description": "Flashcard set content.", + "properties": { + "flashcards_json": { + "additionalProperties": false, + "properties": { + "description": { + "type": "string" + }, + "flashcards": { + "items": { + "additionalProperties": false, + "properties": { + "back": { + "minLength": 1, + "type": "string" + }, + "front": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "front", + "back" + ], + "type": "object" + }, + "maxItems": 200, + "minItems": 1, + "type": "array" + }, + "title": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "title", + "description", + "flashcards" + ], + "type": "object" + } + }, + "required": [ + "flashcards_json" + ], + "type": "object" + }, + "description": { + "description": "Optional short description of the creation (quiz, mock exam, or flashcard set). The note type does not have this field.", + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "creation", + "description": "Must be the string creation. A project source cannot be written with this tool.", + "type": "string" + }, + "title": { + "description": "Title shown to the learner. At least 1 character.", + "minLength": 1, + "type": "string" + }, + "type": { + "const": "flashcard", + "type": "string" + } + }, + "required": [ + "kind", + "title", + "type", + "content" + ], + "type": "object" + } +] - changed
Input schema / properties / project_id / descriptionPrevious value: -"UUID of the Studocu project that will own the artifact."New value: +"UUID of the project that will own the creation. Example: 11111111-1111-4111-8111-111111111111. From create-project or get-context."
- Changed
write-memory3 fields changed- changed
Input schema / properties / kind / descriptionPrevious value: -"Memory kind, e.g. study_preference or project_learning_context."New value: +"Kind for this memory. At least 1 character. Example: \"study_preference\" or \"project_learning_context\". Writing the same kind again replaces the previous memory." - changed
Input schema / properties / project_id / descriptionPrevious value: -"Project UUID for project-local memory; null or omitted stores global (user-level) memory."New value: +"UUID of the project this memory belongs to, or null. Example: 11111111-1111-4111-8111-111111111111. Omit or null to store a learner-wide memory." - changed
Input schema / properties / value / descriptionPrevious value: -"Freeform memory document. MVP convention is { content: string }."New value: +"JSON object to store. Usual shape: { \"content\": \"the memory text\" }. Other keys are allowed."
1 tool update
- Changed
write-artifact2 fields changed- changed
Input schema / properties / artifact / oneOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "content": { - "additionalProperties": false, - "description": "Quiz content.", - "properties": { - "course_id": { - "exclusiveMinimum": 0, - "maximum": 9007199254740991, - "type": "integer" - }, - "questions": { - "items": { - "additionalProperties": false, - "properties": { - "answers": { - "items": { - "additionalProperties": false, - "properties": { - "answer": { - "description": "Answer option text.", - "minLength": 1, - "type": "string" - }, - "is_correct": { - "description": "True for the correct option or options.", - "type": "boolean" - } - }, - "required": [ - "answer", - "is_correct" - ], - "type": "object" - }, - "minItems": 2, - "type": "array" - }, - "difficulty": { - "enum": [ - "EASY", - "MEDIUM", - "HARD" - ], - "type": "string" - }, - "explanation": { - "description": "Required explanation for the correct answer (Core quiz API requires it, max 255 characters).", - "maxLength": 255, - "minLength": 1, - "type": "string" - }, - "question": { - "description": "Question prompt shown to the learner.", - "minLength": 1, - "type": "string" - } - }, - "required": [ - "question", - "answers", - "explanation" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } - }, - "required": [ - "questions" - ], - "type": "object" - }, - "description": { - "description": "Optional description stored on the creation record.", - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "creation", - "description": "Artifact kind. Only creation is writable in this MVP.", - "type": "string" - }, - "title": { - "description": "Human-readable quiz title (Core Labs API requires 20-255 characters).", - "maxLength": 255, - "minLength": 20, - "type": "string" - }, - "type": { - "const": "quiz", - "type": "string" - } - }, - "required": [ - "kind", - "title", - "type", - "content" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "content": { - "additionalProperties": false, - "description": "Lesson content.", - "properties": { - "lesson_json": { - "additionalProperties": false, - "properties": { - "description": { - "type": "string" - }, - "exercises": { - "items": { - "additionalProperties": false, - "properties": { - "concept_explanation": { - "additionalProperties": false, - "properties": { - "paragraph1": { - "minLength": 1, - "type": "string" - }, - "paragraph2": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "paragraph1", - "paragraph2" - ], - "type": "object" - }, - "id": { - "minLength": 1, - "type": "string" - }, - "mcq": { - "items": { - "additionalProperties": false, - "properties": { - "correct_option_id": { - "enum": [ - "A", - "B", - "C", - "D" - ], - "type": "string" - }, - "options": { - "items": { - "additionalProperties": false, - "properties": { - "id": { - "description": "Frontend-supported answer option id.", - "enum": [ - "A", - "B", - "C", - "D" - ], - "type": "string" - }, - "rationale": { - "description": "Rationale shown for this option.", - "minLength": 1, - "type": "string" - }, - "text": { - "description": "Option text.", - "minLength": 1, - "type": "string" - } - }, - "required": [ - "id", - "text", - "rationale" - ], - "type": "object" - }, - "minItems": 2, - "type": "array" - }, - "question": { - "minLength": 1, - "type": "string" - }, - "rationale": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "question", - "options", - "correct_option_id", - "rationale" - ], - "type": "object" - }, - "type": "array" - }, - "open_ended": { - "additionalProperties": false, - "properties": { - "expected_points": { - "items": { - "minLength": 1, - "type": "string" - }, - "minItems": 1, - "type": "array" - }, - "model_answer": { - "minLength": 1, - "type": "string" - }, - "question": { - "minLength": 1, - "type": "string" - }, - "rubric": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "question", - "expected_points", - "model_answer", - "rubric" - ], - "type": "object" - }, - "position": { - "maximum": 9007199254740991, - "minimum": 1, - "type": "integer" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "id", - "position", - "title", - "concept_explanation", - "mcq", - "open_ended" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "outline": { - "additionalProperties": false, - "properties": { - "exercises": { - "items": { - "additionalProperties": false, - "properties": { - "exercise_id": { - "minLength": 1, - "type": "string" - }, - "title": { - "minLength": 1, - "type": "string" - }, - "topic_id": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "exercise_id", - "topic_id", - "title" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "learning_goal": { - "minLength": 1, - "type": "string" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "learning_goal", - "title", - "exercises" - ], - "type": "object" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "title", - "outline", - "exercises" - ], - "type": "object" - } - }, - "required": [ - "lesson_json" - ], - "type": "object" - }, - "description": { - "description": "Optional description stored on the creation record.", - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "creation", - "description": "Artifact kind. Only creation is writable in this MVP.", - "type": "string" - }, - "title": { - "description": "Human-readable title for the created artifact.", - "minLength": 1, - "type": "string" - }, - "type": { - "const": "lesson", - "type": "string" - } - }, - "required": [ - "kind", - "title", - "type", - "content" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "content": { - "additionalProperties": false, - "description": "Mock exam content.", - "properties": { - "exam_json": { - "additionalProperties": false, - "properties": { - "content": { - "items": { - "oneOf": [ - { - "additionalProperties": false, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "instructions": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "section", - "type": "string" - }, - "question_type": { - "description": "Frontend-supported KnowledgeTest question type. Use mcq, not multiple_choice.", - "enum": [ - "mcq", - "multi_select", - "true_false", - "fill_in_blank", - "text_answer_short", - "text_answer_long" - ], - "type": "string" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "kind", - "id", - "question_type" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "stimulus", - "type": "string" - }, - "stimulus_markdown": { - "minLength": 1, - "type": "string" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "kind", - "id", - "stimulus_markdown" - ], - "type": "object" - }, - { - "oneOf": [ - { - "additionalProperties": false, - "properties": { - "grading": { - "additionalProperties": false, - "properties": { - "correct_answer": { - "type": "string" - }, - "correct_answer_ids": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "key_points": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "model_answer": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "model_answer" - ], - "type": "object" - }, - "id": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "question", - "type": "string" - }, - "marks": { - "minimum": 0, - "type": "number" - }, - "options": { - "items": { - "additionalProperties": false, - "properties": { - "id": { - "description": "Stable option id.", - "minLength": 1, - "type": "string" - }, - "text": { - "description": "Option text.", - "minLength": 1, - "type": "string" - } - }, - "required": [ - "id", - "text" - ], - "type": "object" - }, - "minItems": 2, - "type": "array" - }, - "question_markdown": { - "minLength": 1, - "type": "string" - }, - "section_id": { - "minLength": 1, - "type": "string" - }, - "stimulus_id_refs": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "topics": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "type": { - "enum": [ - "mcq", - "multi_select", - "true_false" - ], - "type": "string" - } - }, - "required": [ - "kind", - "id", - "section_id", - "type", - "marks", - "question_markdown", - "options" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "blanks": { - "items": { - "additionalProperties": false, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "label": { - "type": "string" - } - }, - "required": [ - "id" - ], - "type": "object" - }, - "type": "array" - }, - "grading": { - "additionalProperties": false, - "properties": { - "correct_answer": { - "type": "string" - }, - "correct_answer_ids": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "key_points": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "model_answer": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "model_answer" - ], - "type": "object" - }, - "id": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "question", - "type": "string" - }, - "marks": { - "minimum": 0, - "type": "number" - }, - "question_markdown": { - "minLength": 1, - "type": "string" - }, - "section_id": { - "minLength": 1, - "type": "string" - }, - "stimulus_id_refs": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "template_markdown": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "topics": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "type": { - "const": "fill_in_blank", - "type": "string" - } - }, - "required": [ - "kind", - "id", - "section_id", - "type", - "marks", - "question_markdown" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "grading": { - "additionalProperties": false, - "properties": { - "correct_answer": { - "type": "string" - }, - "correct_answer_ids": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "key_points": { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - "model_answer": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "model_answer" - ], - "type": "object" - }, - "id": { - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "question", - "type": "string" - }, - "marks": { - "minimum": 0, - "type": "number" - }, - "question_markdown": { - "minLength": 1, - "type": "string" - }, - "section_id": { - "minLength": 1, - "type": "string" - }, - "stimulus_id_refs": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "topics": { - "anyOf": [ - { - "items": { - "minLength": 1, - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "type": { - "enum": [ - "text_answer_short", - "text_answer_long" - ], - "type": "string" - } - }, - "required": [ - "kind", - "id", - "section_id", - "type", - "marks", - "question_markdown" - ], - "type": "object" - } - ] - } - ] - }, - "minItems": 1, - "type": "array" - }, - "front_matter": { - "additionalProperties": false, - "properties": { - "instructions_markdown": { - "type": "string" - } - }, - "type": "object" - }, - "schema_version": { - "const": "0.8", - "type": "string" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "schema_version", - "title", - "content" - ], - "type": "object" - } - }, - "required": [ - "exam_json" - ], - "type": "object" - }, - "description": { - "description": "Optional description stored on the creation record.", - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "creation", - "description": "Artifact kind. Only creation is writable in this MVP.", - "type": "string" - }, - "title": { - "description": "Human-readable title for the created artifact.", - "minLength": 1, - "type": "string" - }, - "type": { - "const": "mockExam", - "type": "string" - } - }, - "required": [ - "kind", - "title", - "type", - "content" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "content": { - "additionalProperties": false, - "description": "Note content.", - "properties": { - "html": { - "description": "Complete HTML document for the note body (max 1 MiB UTF-8).", - "minLength": 1, - "type": "string" - } - }, - "required": [ - "html" - ], - "type": "object" - }, - "kind": { - "const": "creation", - "description": "Artifact kind. Only creation is writable in this MVP.", - "type": "string" - }, - "title": { - "description": "Human-readable note title (Alpha creation store max 255 characters).", - "maxLength": 255, - "minLength": 1, - "type": "string" - }, - "type": { - "const": "note", - "type": "string" - } - }, - "required": [ - "kind", - "title", - "type", - "content" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "content": { - "additionalProperties": false, - "description": "Flashcard set content.", - "properties": { - "flashcards_json": { - "additionalProperties": false, - "properties": { - "description": { - "type": "string" - }, - "flashcards": { - "items": { - "additionalProperties": false, - "properties": { - "back": { - "minLength": 1, - "type": "string" - }, - "front": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "front", - "back" - ], - "type": "object" - }, - "maxItems": 200, - "minItems": 1, - "type": "array" - }, - "title": { - "minLength": 1, - "type": "string" - } - }, - "required": [ - "title", - "description", - "flashcards" - ], - "type": "object" - } - }, - "required": [ - "flashcards_json" - ], - "type": "object" - }, - "description": { - "description": "Optional description stored on the creation record.", - "minLength": 1, - "type": "string" - }, - "kind": { - "const": "creation", - "description": "Artifact kind. Only creation is writable in this MVP.", - "type": "string" - }, - "title": { - "description": "Human-readable title for the created artifact.", - "minLength": 1, - "type": "string" - }, - "type": { - "const": "flashcard", - "type": "string" - } - }, - "required": [ - "kind", - "title", - "type", - "content" - ], - "type": "object" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "content": { + "additionalProperties": false, + "description": "Quiz content.", + "properties": { + "course_id": { + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" + }, + "questions": { + "items": { + "additionalProperties": false, + "properties": { + "answers": { + "items": { + "additionalProperties": false, + "properties": { + "answer": { + "description": "Answer option text.", + "minLength": 1, + "type": "string" + }, + "is_correct": { + "description": "True for the correct option or options.", + "type": "boolean" + } + }, + "required": [ + "answer", + "is_correct" + ], + "type": "object" + }, + "minItems": 2, + "type": "array" + }, + "difficulty": { + "enum": [ + "EASY", + "MEDIUM", + "HARD" + ], + "type": "string" + }, + "explanation": { + "description": "Required explanation for the correct answer (Core quiz API requires it, max 255 characters).", + "maxLength": 255, + "minLength": 1, + "type": "string" + }, + "question": { + "description": "Question prompt shown to the learner.", + "minLength": 1, + "type": "string" + } + }, + "required": [ + "question", + "answers", + "explanation" + ], + "type": "object" + }, + "minItems": 1, + "type": "array" + } + }, + "required": [ + "questions" + ], + "type": "object" + }, + "description": { + "description": "Optional description stored on the creation record.", + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "creation", + "description": "Artifact kind. Only creation is writable in this MVP.", + "type": "string" + }, + "title": { + "description": "Human-readable quiz title (Core Labs API requires 20-255 characters).", + "maxLength": 255, + "minLength": 20, + "type": "string" + }, + "type": { + "const": "quiz", + "type": "string" + } + }, + "required": [ + "kind", + "title", + "type", + "content" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "content": { + "additionalProperties": false, + "description": "Mock exam content.", + "properties": { + "exam_json": { + "additionalProperties": false, + "properties": { + "content": { + "items": { + "oneOf": [ + { + "additionalProperties": false, + "properties": { + "id": { + "minLength": 1, + "type": "string" + }, + "instructions": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "section", + "type": "string" + }, + "question_type": { + "description": "Frontend-supported KnowledgeTest question type. Use mcq, not multiple_choice.", + "enum": [ + "mcq", + "multi_select", + "true_false", + "fill_in_blank", + "text_answer_short", + "text_answer_long" + ], + "type": "string" + }, + "title": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "kind", + "id", + "question_type" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "id": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "stimulus", + "type": "string" + }, + "stimulus_markdown": { + "minLength": 1, + "type": "string" + }, + "title": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "kind", + "id", + "stimulus_markdown" + ], + "type": "object" + }, + { + "oneOf": [ + { + "additionalProperties": false, + "properties": { + "grading": { + "additionalProperties": false, + "properties": { + "correct_answer": { + "type": "string" + }, + "correct_answer_ids": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "key_points": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "model_answer": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "model_answer" + ], + "type": "object" + }, + "id": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "question", + "type": "string" + }, + "marks": { + "minimum": 0, + "type": "number" + }, + "options": { + "items": { + "additionalProperties": false, + "properties": { + "id": { + "description": "Stable option id.", + "minLength": 1, + "type": "string" + }, + "text": { + "description": "Option text.", + "minLength": 1, + "type": "string" + } + }, + "required": [ + "id", + "text" + ], + "type": "object" + }, + "minItems": 2, + "type": "array" + }, + "question_markdown": { + "minLength": 1, + "type": "string" + }, + "section_id": { + "minLength": 1, + "type": "string" + }, + "stimulus_id_refs": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "topics": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "type": { + "enum": [ + "mcq", + "multi_select", + "true_false" + ], + "type": "string" + } + }, + "required": [ + "kind", + "id", + "section_id", + "type", + "marks", + "question_markdown", + "options" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "blanks": { + "items": { + "additionalProperties": false, + "properties": { + "id": { + "minLength": 1, + "type": "string" + }, + "label": { + "type": "string" + } + }, + "required": [ + "id" + ], + "type": "object" + }, + "type": "array" + }, + "grading": { + "additionalProperties": false, + "properties": { + "correct_answer": { + "type": "string" + }, + "correct_answer_ids": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "key_points": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "model_answer": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "model_answer" + ], + "type": "object" + }, + "id": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "question", + "type": "string" + }, + "marks": { + "minimum": 0, + "type": "number" + }, + "question_markdown": { + "minLength": 1, + "type": "string" + }, + "section_id": { + "minLength": 1, + "type": "string" + }, + "stimulus_id_refs": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "template_markdown": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "topics": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "type": { + "const": "fill_in_blank", + "type": "string" + } + }, + "required": [ + "kind", + "id", + "section_id", + "type", + "marks", + "question_markdown" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "grading": { + "additionalProperties": false, + "properties": { + "correct_answer": { + "type": "string" + }, + "correct_answer_ids": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "key_points": { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + "model_answer": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "model_answer" + ], + "type": "object" + }, + "id": { + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "question", + "type": "string" + }, + "marks": { + "minimum": 0, + "type": "number" + }, + "question_markdown": { + "minLength": 1, + "type": "string" + }, + "section_id": { + "minLength": 1, + "type": "string" + }, + "stimulus_id_refs": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "topics": { + "anyOf": [ + { + "items": { + "minLength": 1, + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "type": { + "enum": [ + "text_answer_short", + "text_answer_long" + ], + "type": "string" + } + }, + "required": [ + "kind", + "id", + "section_id", + "type", + "marks", + "question_markdown" + ], + "type": "object" + } + ] + } + ] + }, + "minItems": 1, + "type": "array" + }, + "front_matter": { + "additionalProperties": false, + "properties": { + "instructions_markdown": { + "type": "string" + } + }, + "type": "object" + }, + "schema_version": { + "const": "0.8", + "type": "string" + }, + "title": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "schema_version", + "title", + "content" + ], + "type": "object" + } + }, + "required": [ + "exam_json" + ], + "type": "object" + }, + "description": { + "description": "Optional description stored on the creation record.", + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "creation", + "description": "Artifact kind. Only creation is writable in this MVP.", + "type": "string" + }, + "title": { + "description": "Human-readable title for the created artifact.", + "minLength": 1, + "type": "string" + }, + "type": { + "const": "mockExam", + "type": "string" + } + }, + "required": [ + "kind", + "title", + "type", + "content" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "content": { + "additionalProperties": false, + "description": "Note content.", + "properties": { + "html": { + "description": "Complete HTML document for the note body (max 1 MiB UTF-8).", + "minLength": 1, + "type": "string" + } + }, + "required": [ + "html" + ], + "type": "object" + }, + "kind": { + "const": "creation", + "description": "Artifact kind. Only creation is writable in this MVP.", + "type": "string" + }, + "title": { + "description": "Human-readable note title (Alpha creation store max 255 characters).", + "maxLength": 255, + "minLength": 1, + "type": "string" + }, + "type": { + "const": "note", + "type": "string" + } + }, + "required": [ + "kind", + "title", + "type", + "content" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "content": { + "additionalProperties": false, + "description": "Flashcard set content.", + "properties": { + "flashcards_json": { + "additionalProperties": false, + "properties": { + "description": { + "type": "string" + }, + "flashcards": { + "items": { + "additionalProperties": false, + "properties": { + "back": { + "minLength": 1, + "type": "string" + }, + "front": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "front", + "back" + ], + "type": "object" + }, + "maxItems": 200, + "minItems": 1, + "type": "array" + }, + "title": { + "minLength": 1, + "type": "string" + } + }, + "required": [ + "title", + "description", + "flashcards" + ], + "type": "object" + } + }, + "required": [ + "flashcards_json" + ], + "type": "object" + }, + "description": { + "description": "Optional description stored on the creation record.", + "minLength": 1, + "type": "string" + }, + "kind": { + "const": "creation", + "description": "Artifact kind. Only creation is writable in this MVP.", + "type": "string" + }, + "title": { + "description": "Human-readable title for the created artifact.", + "minLength": 1, + "type": "string" + }, + "type": { + "const": "flashcard", + "type": "string" + } + }, + "required": [ + "kind", + "title", + "type", + "content" + ], + "type": "object" + } +] - changed
Output schema / properties / type / enumPrevious value: -[ - "quiz", - "mockExam", - "lesson", - "note", - "flashcard" -]New value: +[ + "quiz", + "mockExam", + "note", + "flashcard" +]
1 tool update
- Changed
search-documents1 field changed- added
Output schema / properties / documents / items / properties / match_typeAdded value: +{ + "const": "semantic", + "type": "string" +}
1 tool update
- Changed
search-documents3 fields changed- added
Input schema / properties / use_no_course_as_fallbackAdded value: +{ + "description": "Only used with `course_id`. When true and that course has no matching documents, search again without the course, so results may come from other courses; check each result's `course_id`. Default false.", + "type": "boolean" +} - added
Output schema / properties / documents / items / properties / course_idAdded value: +{ + "type": "number" +} - added
Output schema / properties / documents / items / properties / institution_idAdded value: +{ + "type": "number" +}
2 tool updates
- Removed
read-web-url - Removed
search-web
20 tool updates
- First observed
add-document-sources - First observed
agent-os-session - First observed
create-project - First observed
delete-memory - First observed
get-context - First observed
get-course-mastery - First observed
get-course-syllabus - First observed
get-project-state - First observed
read-artifact - First observed
read-detached-document - First observed
read-memory - First observed
read-web-url - First observed
request-creation - First observed
search-courses - First observed
search-documents - First observed
search-institutions - First observed
search-web - First observed
update-project - First observed
write-artifact - First observed
write-memory
Publisher details
- Operator
- Studocu's team · Publisher source
- Operator website
- https://www.studocu.com/mcp · Publisher source
- Vendor relationship
- Not applicable
- Documentation
- https://www.studocu.com/mcp · Publisher source
- Trust center
- Not applicable
- Restrictions
- Not available
Related MCP Connectors
Search university course materials, your flashcards, quizzes, streak and quota. All tools read-only.
Search 18M+ legal documents worldwide — case law, legislation, and doctrine across 110+ countries.
Free study plans, thesis statements and citations. Quizzes, flashcards and AI tutor need an account.
Tasks, calendar and study materials in Toddyi: search, read and plan with your tasks.
Related MCP Servers
- FlicenseAqualityDmaintenanceExposes course documents as searchable resources and provides tools for reading, study task management, and source-grounded quiz prompts. Supports hybrid retrieval and integration with DeepSeek-based agents.51-
- AlicenseAqualityBmaintenanceEnables searching your local study notes, course code, and lecture PDFs, reading files and PDF pages, registering doubts, and tracking completed lessons. Also provides prompts to generate quizzes and weekly revision plans grounded in your own material with source citations.5ISC
- FlicenseNot gradedqualityDmaintenanceProvides full-text search and context retrieval from university course materials (PDF, PPTX, DOCX) offline after indexing.-
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.