Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Create registry project

create_registry_project

Create an extra project on the organisation's Ankra registry (the twin of ankra registry projects create), private and under the same scan, retention and storage policy as its own project. A name is 2 to 30 lower-case letters, digits and single hyphens. Requires credentials.write.

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": {
      "name": "<name>"
    },
    "name": "create_registry_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe new project's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the project is private, inherits scan/retention/storage policy, and requires credentials.write. It does not explain duplicate-name handling or failure behavior, but the added operational context is substantial.

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 three short, front-loaded sentences: the operation, the naming rule, then the permission requirement. Every sentence contributes useful information and nothing is redundant.

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 one-parameter mutation with full schema coverage and safety annotations, the description covers naming, visibility, inherited policies, and required credentials. It leaves return behavior unstated, but with no output schema this is not essential to invoking the tool correctly.

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 input schema already documents the single name parameter at full coverage, and the description meaningfully adds validation rules: 2–30 lower-case letters, digits, and single hyphens. It does not say whether the name must be unique, so it falls just short of complete parameter semantics.

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 uses a specific verb and resource: it says to create an extra project on the organisation's Ankra registry, explicitly tying the action to registry projects rather than generic projects. The CLI twin reference further anchors the operation.

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 gives clear usage context by saying this creates an additional registry project under the organisation's existing policies and requires credentials.write. It does not explicitly state when to choose this over create_project or list_registry_projects, so routing among siblings is left to inference.

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

All Ankra toolsInspect
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