Skip to main content
Glama

Little Works

project_to_bookable_package

Turn a completed Little Works project (photos + notes) into a draft Recipe, Bill of Materials, and homeowner booking intake — same Gemini multimodal engine as Message “AI Project Manager”. Requires OAuth or apiKey; writes under actingAsUid.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
slugNoPublic slug, e.g. siding-a-house
briefNoOperator brief / full PM prompt
titleNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
projectIdNoFirestore entity id, e.g. project_…
bookingUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does add meaningful context: OAuth or apiKey authentication is required, and the operation writes under actingAsUid. However, it does not disclose whether the operation is idempotent, what happens on repeat invocation, whether existing recipes or bookings are overwritten, or any cost/rate characteristics of the Gemini multimodal engine — all relevant for an unannotated write tool.

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?

Two dense sentences, front-loaded with the core transformation before the engine and auth details. The 'same Gemini multimodal engine as Message AI Project Manager' clause is somewhat incidental but plausibly useful for expectation-setting, so little is wasted.

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?

There is no output schema, and the description does name the three artifacts produced, which is the most important return-value context. Still, it does not clarify the minimum viable call (zero required params means an agent cannot infer which inputs are actually needed) or the relationship between the generated draft and downstream booking/materials tools.

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?

Only apiKey is echoed from the description, and its meaning is already given in the schema. The description says nothing about how projectId versus slug selects the target, what brief (the 'full PM prompt') controls, or what city, title, and bookingUrl affect in the generated package. With 57% schema coverage and seven loosely required parameters, the description does not compensate for the undocumented ones.

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

Purpose4/5

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

The description uses a specific transformation verb and names three concrete outputs (draft Recipe, Bill of Materials, homeowner booking intake) from a specific input (a completed Little Works project with photos and notes). It is clearly distinguishable from generic readers like get_project, though it never directly names or rules out adjacent siblings such as create_booking or draft_materials_order.

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?

The phrase 'completed Little Works project' gives an implicit precondition for use, which is real but minimal guidance. There is no statement of when to prefer this over the sibling tools that create bookings or draft material orders, and no note on what to do if the project is not yet complete or already converted.

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