Skip to main content
Glama

Create project

create_project

Create a new billing project under one of your customers. The organization is fixed by your context; customer_id must be a customer in your organization. Discover ids with find_billing_work - never ask the user for an id.

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": {
      "customer_id": "<customer_id>",
      "name": "<name>",
      "billing_type": "<billing_type>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProject name (required).
customer_idYesId of the customer this project belongs to (required). Must be a customer in your organization.
descriptionNoOptional project description (max 500 characters).
billing_typeYesBilling type to allow on the project (required). One of: TM, Fix, OVH.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
create_general_activityNoOptional. When true (the default for this tool), also create a default visible "General" task + activity so time can be logged on the project immediately. Set false to create an empty project with no activities yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / description / description
      Previous value: -"Optional project description (max 1000 characters)."New value: +"Optional project description (max 500 characters)."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation profile is known. The description adds real value by disclosing the default side effect of creating a 'General' task and activity, but it says nothing about permissions, failure modes, or what is returned. Note the schema offers an idempotency_key while idempotentHint=false, and the description does not reconcile this, leaving retry safety ambiguous.

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?

Three short sentences, front-loaded with the scope constraint, then the id-discovery rule. Every sentence carries actionable information and there is no restatement of the title or schema.

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 six-parameter mutation with full schema coverage and annotations, the description covers scoping, id discovery, and the default activity side effect. The one meaningful gap is the absence of an output schema combined with no statement of what a successful call returns (e.g. the new project id), which an agent would need for chaining.

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 100%, so the baseline is 3. The description goes beyond the schema by stating that customer_id must resolve to a customer in the caller's organization and by naming find_billing_work as the way to obtain ids, which is procedural meaning the schema does not carry.

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 opens with a specific verb and resource ('Create a new billing project') and immediately narrows scope ('under one of your customers', 'organization is fixed by your context'). This separates it from sibling mutations like create_customer or update_project without the agent needing to open any schema.

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 an explicit prerequisite workflow ('Discover ids with find_billing_work - never ask the user for an id') and a validation constraint on customer_id. It stops short of saying when to choose this over alternatives such as update_project or create_customer, so it is clear context without full when/when-not routing.

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.

Resources