Skip to main content
Glama

Create Studocu Project

create-project

Create a new project. Every field is optional. Returns project_id for add-document-sources, write-artifact, and request-creation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create-project"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiNoIcon text, usually an emoji. Example: "📚". Omit to leave the icon unset.
titleNoName, 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_idNoPositive 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

NameRequiredDescriptionDefault
urlNoStudocu web link to the project, for the user to open. Returned to external MCP clients only.
emojiYes
titleYesAgent-displayable project title. Null Alpha names become "Untitled project".
course_idYes
is_mobileYes
project_idYesUUID string in 8-4-4-4-12 hexadecimal form. Example: 11111111-1111-4111-8111-111111111111.
institution_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / url
      Added value: +{
      +  "description": "Studocu web link to the project, for the user to open. Returned to external MCP clients only.",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • addedInput schema / properties / course_id / description
      Added 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."
    • addedInput schema / properties / emoji / description
      Added value: +"Icon text, usually an emoji. Example: \"📚\". Omit to leave the icon unset."
    • addedInput schema / properties / title / description
      Added 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\"."
    • changedOutput schema / properties / project_id / description
      Previous 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."
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-idempotent, non-destructive, closed-world write. The description adds two genuinely new facts: every field is optional (creation always succeeds with no arguments) and the returned project_id feeds three named tools. It says nothing about what a fresh project contains by default or about permission/ownership requirements.

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, front-loaded with the verb and scope, followed by the optionality fact and the downstream ID consumers. Nothing is redundant or padded.

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 create tool with full schema coverage, annotations, and an output schema, the description covers purpose, optionality, and how the returned ID is used downstream. It leaves only edge behavior (duplicate names, empty project contents) unaddressed, which is minor at this complexity.

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

Parameters4/5

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

Schema description coverage is 100% and each parameter's semantics are fully documented in the schema. The description's one addition, "Every field is optional," is a footprint-level fact the agent benefits from at a glance, but it does not add per-parameter meaning.

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" states a specific verb and resource, and the mention of returning project_id for add-document-sources, write-artifact, and request-creation positions it as the entry point of the workflow. It does not explicitly contrast with update-project, so the agent must infer the create-vs-modify distinction.

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?

Naming the three downstream tools that consume project_id implies this is the tool to call before adding sources or artifacts, which is useful workflow guidance. There is no explicit when-not or prerequisite statement (e.g., that a course must exist first, or that update-project handles existing projects).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources