Create a new project by providing required name and description, with optional verbosity and session ID settings.
Creates a new project. verbosity: 'minimal', 'standard' (default), 'full'. Uses default session if session_id not provided.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| description | Yes | ||
| kwargs | No | ||
| session_id | No | ||
| verbosity | No | standard |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v2.0.1Input schema / properties / kwargs / defaultAdded value: +nullInput schema / properties / kwargs / titlePrevious value: -"kwargs"New value: +"Kwargs"Input schema / properties / kwargs / typeRemoved value: -"string"Input schema / properties / session_id / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / session_id / defaultAdded value: +nullInput schema / properties / session_id / typeRemoved value: -"string"Input schema / properties / verbosityAdded value: +{
+ "default": "standard",
+ "title": "Verbosity",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "session_id",
- "name",
- "description",
- "kwargs"
-]New value: +[
+ "name",
+ "description"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "result": {
+ "additionalProperties": true,
+ "title": "Result",
+ "type": "object"
+ }
+ },
+ "required": [
+ "result"
+ ],
+ "title": "create_projectOutput",
+ "type": "object"
+}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description does not disclose behavioral traits such as permissions, idempotency, or side effects beyond creation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two efficient sentences, front-loaded with purpose, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate given output schema existence, but lacks explanation of error cases or relationship to other create tools; could mention required fields.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description adds value by explaining verbosity levels and session default, but leaves kwargs unexplained and no parameter constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Creates a new project,' specifying a verb and resource distinct from sibling tools like update_project and delete_project.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Mentions verbosity options and default session behavior, providing implied usage context, but lacks explicit when-to-use vs alternatives like bulk_create_*.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/talhaorak/pytaiga-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server