Skip to main content
Glama

Create a project

runheed_create_project

Creates a project in the workspace and returns its DSN: the value an app sets as the RUNHEED_DSN environment variable so that runheed.init() reports its errors to this project.

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": "runheed_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProject name, usually the app or service name, for example shop-api
slugNoOptional URL-safe slug; derived from the name when left out
platformNoThe app's platform

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds genuinely useful behavior beyond that: the call returns a DSN and explains exactly what the caller should do with it (set RUNHEED_DSN so runheed.init() reports here). It stops short of disclosing what happens on name/slug collision, which matters given idempotentHint=false.

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 front-loaded sentence with the core action first and the return-value explanation trailing. No filler, no restatement of the title, and every clause contributes new information.

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-parameter creation tool with full schema coverage, no output schema, and annotations covering the safety profile, the description covers the essential gap — what the call returns and why it matters. The only notable omission is failure/duplicate handling for a non-idempotent create.

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 description coverage is 100%, so name, slug and platform are already fully documented, including the slug-from-name derivation and the platform enum. The description adds nothing about parameters, so the baseline 3 applies.

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 ('Creates a project in the workspace') and goes further by naming the return value (the DSN) and its downstream purpose. An agent can distinguish this from the read-oriented siblings such as runheed_list_projects or runheed_get_project_health purely from the description.

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?

Usage is only implied through the DSN/runheed.init() explanation, which signals this is the onboarding step for wiring an app to error reporting. There is no explicit when-to-use, no prerequisites (e.g. workspace membership), and no stated alternative or exclusion such as how to handle an already-existing project.

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.