Planner (proof-of-done)

project-create

Create a new project container for goals. Requires title and a unique slug (lowercase a-z, 0-9, hyphens). Optional: description, status (active/archived/paused, default active), tags, icon (emoji), repositoryPath, repositoryUrl, sourceRef ({type:"git",url,ref} — remote-research source), isDefault. Returns the created project with id, slug, and webUrl. Slug must be unique — duplicates are rejected with existing slugs list.

Input Schema

TableJSON Schema

Name	Required	Description
`icon`	No	Иконка (эмодзи, макс. 10 символов)
`slug`	Yes	Уникальный slug (только a-z, 0-9, дефис)
`tags`	No	Теги
`title`	Yes	Название проекта
`status`	No	Статус: active / archived / paused (default: active)
`isDefault`	No	Сделать проектом по умолчанию
`sourceRef`	No	Источник кода для remote-research: {type:"git",url,ref}
`description`	No	Описание проекта
`repositoryUrl`	No	URL репозитория
`repositoryPath`	No	Путь к репозиторию на сервере

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 9, 2026

addedInput schema / properties / sourceRef

Added value: +{
+  "default": null,
+  "description": "Источник кода для remote-research: {type:\"git\",url,ref}",
+  "type": "object"
+}

AddedJun 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only indicate this mutates and is not idempotent. The description adds significant value: it states the created project is returned with id, slug, and webUrl, and discloses that duplicate slugs are rejected with a list of existing slugs. This is exactly the kind of behavioral context an agent needs.

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?

A single dense paragraph with no filler. The opening sentence states the core purpose, followed by requirements, optional fields, return value, and uniqueness behavior. Every sentence earns its place.

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 10-parameter creation tool with no output schema, the description covers the required/optional split, defaults, slug constraints, duplicate handling, return fields, and nested sourceRef format. Combined with 100% schema description coverage, an agent has everything needed to call it correctly.

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 the baseline is 3. The description mostly restates schema constraints such as slug character rules, status options, and sourceRef shape rather than adding genuinely new semantics. It is a useful English summary of Russian schema descriptions, but it does not go beyond them substantively.

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: 'Create a new project container for goals.' The phrase 'container for goals' distinguishes it from goal-create and other goal-* siblings, and 'project-create' is clearly distinct from project-update, project-get, project-list, and project-delete.

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?

Provides clear context: this tool is for creating a new project, with required fields and defaults. It does not explicitly name alternatives like project-update or goal-create or state when not to use it, so it stops short of full exclusion guidance.

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

All Planner (proof-of-done) tools Inspect

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.

Resources

Need Help?