Skip to main content
Glama
Cafelatte1

FronyBoard

by Cafelatte1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_project

Register a codebase as a tracked project before planning starts, setting its task-ID prefix, description, and repo so tasks and roadmap items can be created and shown on the dashboard.

Instructions

Use it when the user wants a codebase tracked here (register a project, set up a board).

Register a new project — once per codebase, before any planning happens.

`key` is the task-id prefix (2-5 uppercase letters, e.g. DLY); `description` is one
line saying what the project is, in the user's language (shown on the dashboard cards);
`repo` is where its code lives (owner/name or a URL). Status starts as active.

A fresh project takes tasks at once: create_task opens the current quarter. The plan
(set_overview, upsert_milestone) is optional and written with the user.

Input Schema

NameRequiredDescriptionDefault
keyYes
nameNo
repoNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose useful state facts (status starts as active, the project accepts tasks immediately, create_task opens the current quarter). It omits duplicate-key behavior, required permissions, and whether `key` is immutable — meaningful gaps for a create operation.

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?

Front-loaded with the trigger sentence, then the operation, then per-parameter notes — good ordering with no filler sentences. The closing paragraph on optional planning is mildly tangential but earns its place by preventing premature set_overview/upsert_milestone calls.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description is the only source of truth; it covers behavior and most parameters but leaves `name` unexplained (unclear how it differs from `description`) and says nothing about what is returned or what happens on a key collision.

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 0%, so the description must compensate, and it does for three of four parameters: `key` gets format rules and an example (2-5 uppercase letters, DLY), `description` gets length, language, and where it renders, and `repo` gets accepted formats (owner/name or URL). Only `name` is left entirely undefined.

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 ('Register a new project') plus a scope qualifier ('once per codebase, before any planning happens') that separates it from update_project and list_projects. An agent can identify the operation and its one-shot nature without opening the 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?

Opens with an explicit trigger ('Use it when the user wants a codebase tracked here') and adds a strong constraint ('once per codebase, before any planning happens') that implies when not to call it. It also names the follow-on siblings (create_task, set_overview, upsert_milestone), but never says what to do if the project already exists (e.g., route to update_project).

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

Deploy Server

Other Tools