Skip to main content
Glama

Little Works

start_project

Start a project. Pass brief + optional projectId/slug to package an existing completed job into a bookable service (shared writer). Otherwise returns the build landing stub.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
slugNo
briefNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
projectIdNo
bookingUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / apiKey
      Added value: +{
      +  "description": "Required when LITTLEWORKS_MCP_API_KEY is set on the server",
      +  "type": "string"
      +}
    • addedInput schema / properties / bookingUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / brief
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / city
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / projectId
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior. It mentions two outcomes and 'shared writer,' but does not explain side effects, permissions, API key requirements, idempotency, or what happens when parameters are omitted or invalid.

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?

The description is short and front-loads the main action before the conditional behavior. The first sentence is somewhat redundant, but the second sentence carries the substantive detail efficiently.

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

Completeness2/5

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

This is a six-parameter tool with no annotations, no output schema, and very low schema description coverage. The description covers the main branch only partially and leaves key parameters, return behavior, and operational semantics unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, so the description should compensate. It clarifies brief, projectId, and slug in the packaging branch, but says nothing about city or bookingUrl, and only the schema briefly covers apiKey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening 'Start a project' is broad and mostly restates the tool name. The second sentence adds two concrete modes, packaging a completed job or returning a build landing stub, but the overall purpose remains somewhat opaque, especially what 'project' and 'build landing stub' mean.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an input-dependent branch, but does not state when to use this tool versus alternatives such as project_to_bookable_package or start_recipe. There is no explicit guidance on prerequisites, exclusions, or the intended decision path beyond passing brief/projectId/slug.

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