Skip to main content
Glama

Create or attach to a project

saveToProject

Create a project (create), attach lots (attach_parcels), or attach a knowledge reference (attach_reference). Pass projectId or project; with neither, the result lists projects and writes nothing. For attach_parcels, pass a WGS84 GeoJSON polygon (up to 500 selected parcels), or copy lot.parcelExternalId from checkSite. Polygon cannot be combined with parcelExternalIds or radiusM. Results report source truncation and attached count. preview=true returns the diff and writes nothing. A write returns a receipt. Not reversible on this surface.

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": {
      "action": "<action>",
      "context": "<context>"
    },
    "name": "saveToProject"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude from checkSite. Supplied coordinates are never re-geocoded.
lngNoLongitude from checkSite.
nameNo
roleNobuild is the lot being developed; context is surrounding land. Default build.
actionYescreate: new project from a site. attach_parcels: attach lots to an existing project (use lot.parcelExternalId from screenLots or checkSite). attach_reference: link a knowledge section to an existing project.
addressNoStreet address of the site. On `create` this is geocoded server-side when lat/lng are not supplied, and is what gets recorded as the project address.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
polygonNoWGS84 GeoJSON Polygon for attach_parcels. Attach the parcels selected by the product area flow, up to 500. Interior rings exclude parcels. Use polygon instead of parcelExternalIds and radiusM. Maximum 512 coordinates.
previewNoWhen true, return the field-level diff and write nothing.
projectNoProject name to match instead of a UUID, for attach_parcels and attach_reference. Matching more than one lists the candidates instead of guessing. Ignored by create.
radiusMNoSearch half-width in metres when resolving parcel ids. Default 150.
projectIdNoExisting project UUID. Required by attach_parcels and attach_reference unless you pass `project`; ignored by create.
externalRefNoProvenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Returned on getProjectContext. Distinct from idempotencyKey.
sectionUuidNo
idempotencyKeyNo
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
parcelExternalIdsNoSource parcel ids to attach. Copy lot.parcelExternalId from screenLots or checkSite; no checkSite call is needed for lots screenLots returned. If they are not in the current area, pass a larger radiusM on attach_parcels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"create: new project from a site. attach_parcels: attach lots to an existing project (use lot.parcelExternalId from checkSite). attach_reference: link a knowledge section to an existing project."New value: +"create: new project from a site. attach_parcels: attach lots to an existing project (use lot.parcelExternalId from screenLots or checkSite). attach_reference: link a knowledge section to an existing project."
    • changedInput schema / properties / parcelExternalIds / description
      Previous value: -"Source parcel ids to attach. Copy lot.parcelExternalId from checkSite. If they are not in the current area, pass a larger radiusM on attach_parcels."New value: +"Source parcel ids to attach. Copy lot.parcelExternalId from screenLots or checkSite; no checkSite call is needed for lots screenLots returned. If they are not in the current area, pass a larger radiusM on attach_parcels."
  2. Changed1 schema field changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""New value: +"A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details."
  4. Changed4 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"create: new project from a site. attach_parcels: attach lots to an existing project (use lot.parcelExternalId from getFeasibilitySnapshot). attach_reference: link a knowledge section to an existing project."New value: +"create: new project from a site. attach_parcels: attach lots to an existing project (use lot.parcelExternalId from checkSite). attach_reference: link a knowledge section to an existing project."
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude from getFeasibilitySnapshot. Supplied coordinates are never re-geocoded."New value: +"Latitude from checkSite. Supplied coordinates are never re-geocoded."
    • changedInput schema / properties / lng / description
      Previous value: -"Longitude from getFeasibilitySnapshot."New value: +"Longitude from checkSite."
    • changedInput schema / properties / parcelExternalIds / description
      Previous value: -"Source parcel ids to attach. Copy lot.parcelExternalId from getFeasibilitySnapshot. If they are not in the current area, pass a larger radiusM on attach_parcels."New value: +"Source parcel ids to attach. Copy lot.parcelExternalId from checkSite. If they are not in the current area, pass a larger radiusM on attach_parcels."
  5. Changed2 schema fields changed
    • removedInput schema / properties / polygon / additionalProperties
      Removed value: -false
    • changedInput schema / required
      Previous value: -[
      -  "action",
      -  "preview",
      -  "context"
      -]New value: +[
      +  "action",
      +  "context"
      +]
  6. Changed2 schema fields changed
    • removedInput schema / properties / llm_model
      Removed value: -{
      -  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "action",
      -  "preview",
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "action",
      +  "preview",
      +  "context"
      +]
  7. Changed2 schema fields changed
    • removedInput schema / properties / conversation_id
      Removed value: -{
      -  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      -  "type": "string"
      -}
    • addedInput schema / properties / polygon
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "WGS84 GeoJSON Polygon for attach_parcels. Attach the parcels selected by the product area flow, up to 500. Interior rings exclude parcels. Use polygon instead of parcelExternalIds and radiusM. Maximum 512 coordinates.",
      +  "properties": {
      +    "coordinates": {
      +      "items": {
      +        "items": {
      +          "items": {
      +            "type": "number"
      +          },
      +          "maxItems": 2,
      +          "minItems": 2,
      +          "type": "array"
      +        },
      +        "maxItems": 512,
      +        "minItems": 4,
      +        "type": "array"
      +      },
      +      "maxItems": 128,
      +      "minItems": 1,
      +      "type": "array"
      +    },
      +    "type": {
      +      "const": "Polygon",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "type",
      +    "coordinates"
      +  ],
      +  "type": "object"
      +}
  8. Changed5 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / properties / parcelExternalIds / description
      Previous value: -"Source parcel ids to attach. Copy lot.parcelExternalId from getFeasibilitySnapshot, or from bucky parcels search."New value: +"Source parcel ids to attach. Copy lot.parcelExternalId from getFeasibilitySnapshot. If they are not in the current area, pass a larger radiusM on attach_parcels."
    • changedInput schema / required
      Previous value: -[
      -  "action",
      -  "preview",
      -  "context"
      -]New value: +[
      +  "action",
      +  "preview",
      +  "context",
      +  "llm_model"
      +]
  9. Changed2 schema fields changed
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Project name to match instead of a UUID, for attach_parcels and attach_reference. Matching more than one lists the candidates instead of guessing. Ignored by create.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / projectId / description
      Added value: +"Existing project UUID. Required by attach_parcels and attach_reference unless you pass `project`; ignored by create."
  10. Changed4 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Street address of the site. On `create` this is geocoded server-side when lat/lng are not supplied, and is what gets recorded as the project address."
    • addedInput schema / properties / externalRef
      Added value: +{
      +  "description": "Provenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Returned on getProjectContext. Distinct from idempotencyKey.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / lat / description
      Added value: +"Latitude from getFeasibilitySnapshot. Supplied coordinates are never re-geocoded."
    • addedInput schema / properties / lng / description
      Added value: +"Longitude from getFeasibilitySnapshot."
  11. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses several behaviors the agent could not infer: preview returns a field-level diff and writes nothing, results report source truncation and attached count, a write returns a receipt, and the change is not reversible on this surface. The irreversibility note is a useful nuance against destructiveHint=false (an additive create is not a destructive update), not a contradiction of it.

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?

Front-loaded with the mode enumeration, then the required-argument rule, then per-mode constraints, then return/preview semantics. Each sentence carries a distinct operational fact with no restatement of the title or name.

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 17-parameter, nested-polygon, three-mode tool with no output schema, the description covers the write-safety story, the read fallback, and the shape of results (truncation, attached count, receipt, diff). Gaps are minor: it does not say what `create` returns (e.g. a project id) or what idempotencyKey does on this surface.

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 82%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not fully carry: the projectId/project fallback that degenerates into a read, the 500-parcel cap, copying `lot.parcelExternalId` from checkSite/screenLots, and how ambiguous `project` names are resolved. It leaves secondary fields (sectionUuid, idempotencyKey, externalRef, role) to the schema.

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 precise enumeration of the three modes (`create`, `attach_parcels`, `attach_reference`) and what each one does, so the agent can distinguish them without opening the schema. It also names the sibling sources (`checkSite`, `screenLots`) that supply the ids each mode needs.

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

Usage Guidelines5/5

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

It states the selection rule explicitly: pass `projectId` or `project`, and with neither the call lists projects and writes nothing. It also gives the mutual-exclusion rule (polygon cannot be combined with parcelExternalIds or radiusM) and the safe-trial path (`preview=true`), which is exactly the when/when-not guidance an agent needs.

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.