Umtri

Create a new ground (project)

create_project

Creates a new ground. Slug must match /^[a-z0-9][a-z0-9-]{0,49}$/ and be unique. By default it goes into the authenticated user's personal space; pass org (a team slug, as list_projects shows it) to create it in a team — only the team's owner can. Requires a write-scope token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "name": "<name>"
    },
    "name": "create_project"
  }
}

Input Schema

Name	Required	Description
`org`	No	Team slug to create the ground in. Omit for your personal space. You must own the team.
`name`	Yes	Display name.
`slug`	Yes	URL slug. Lowercase letters, digits, hyphens; 1–50 chars.
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the write-scope token requirement, the uniqueness constraint on slug, the personal-vs-team routing, and the ownership permission gate. It does not say what a slug collision returns, whether the name must be unique, or what the call returns, which are the remaining gaps for a mutation.

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 tight sentences with the core action first, then validation, then routing and auth. The slug regex is restated verbatim from the schema, which is mild duplication, but nothing else is wasted.

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 4-parameter create tool with no output schema and no annotations, the description covers the constraints an agent needs to call it correctly: slug format and uniqueness, org routing, ownership, and token scope. Missing return-value expectations and error behavior on conflict keep it short of full completeness.

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 75% and the description still adds meaning the schema lacks: slug uniqueness (not expressed in JSON Schema) and the team-ownership prerequisite plus the pointer to list_projects for obtaining the org value. The undocumented 'description' parameter is the one field not covered by either source.

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 opens with a specific verb+resource ("Creates a new ground"), and the surrounding rules (slug, org, token) make clear this is the workspace/team creation entry point. The only wrinkle is that "ground" is domain jargon that never says "project" in the description body, so an agent must infer the equivalence with the title and the list_projects sibling.

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 states the default path (authenticated user's personal space) and the condition for the alternative (pass org with a team slug, only as team owner), plus points to list_projects as the way to discover a team slug. There are no exclusions or 'do not use' cases, but no sibling tool competes for this action.

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

All Umtri 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.