Skip to main content
Glama

Update site

update_site
DestructiveIdempotent

Update an existing site by ID, or archive / restore it with archived. Archiving a site archives its buildings, locations and assets in one step and keeps every linked work order; prefer it to delete_site for a closed site. Requires sites:write scope.

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": {
      "id": "<id>"
    },
    "name": "update_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSite ID
cityNoCity
nameNoSite name
addressNoStreet address
countryNoCountry
archivedNotrue archives the site with its buildings, locations and assets; false restores it and what was archived with it. Confirm with the user first.
provinceNoProvince/state
year_builtNoYear built
descriptionNoDescription
postal_codeNoPostal/zip code
contact_nameNoPrimary contact name
contact_emailNoContact email
contact_phoneNoContact phone
cost_per_sqftNoBase cost per square foot
lease_detailsNoFree-text lease details / notes
lease_end_dateNoLease end date (YYYY-MM-DD)
owner_landlordNoProperty owner or landlord
ownership_typeNoOwnership type
renewal_optionNoLease renewal option details
square_footageNoSquare footage
archived_reasonNoOptional reason, only with archived: true
lease_start_dateNoLease start date (YYYY-MM-DD)
insurance_providerNoInsurance provider name
insurance_policy_numberNoInsurance policy number
additional_cost_per_sqftNoAdditional cost per square foot
property_manager_companyNoProperty management company name
operational_cost_per_sqftNoOperational cost per square foot
property_manager_contact_nameNoProperty management contact name
property_manager_contact_emailNoProperty management contact email
property_manager_contact_phoneNoProperty management contact phone

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / archived
      Added value: +{
      +  "description": "true archives the site with its buildings, locations and assets; false restores it and what was archived with it. Confirm with the user first.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / archived_reason
      Added value: +{
      +  "description": "Optional reason, only with archived: true",
      +  "enum": [
      +    "closed",
      +    "sold",
      +    "lease_ended",
      +    "merged",
      +    "other"
      +  ],
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  3. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  4. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  5. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, yet the description still adds critical information the agent could not infer: the cascade to buildings, locations and assets, the fact that linked work orders survive, and the required `sites:write` scope. That is exactly the value-add the lower bar for annotated tools should reward.

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 sentences, no padding, and the primary update-by-ID purpose leads before the archive behavior and the delete comparison. Every clause carries an operational fact.

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 destructive 30-parameter mutation with no output schema, the description covers cascade effects, data survival, auth scope and the sibling alternative. The remaining gap is that partial-update semantics — that omitted fields are left unchanged — are never stated, which matters for a tool with one required parameter among thirty.

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

Parameters3/5

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

Schema coverage is 100% across 30 parameters, so the schema already documents every field, including lengths, enums and the archived_reason constraint. The description mentions `id` and `archived` but adds no interpretation beyond what the schema's own `archived` text already says, so it earns the baseline rather than more.

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 (update an existing site by ID) and covers the alternate modes (archive/restore via `archived`) in the same sentence. It explicitly distinguishes itself from `delete_site`, so an agent with a site-closure intent can pick correctly without opening a 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?

Gives an explicit routing rule: for a closed site, prefer archiving over `delete_site`, because archiving preserves linked work orders. It does not address when to use this versus `bulk_update` or `bulk_create` for multi-site edits, but the one exclusion it does state is decisive for the highest-risk case.

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