Skip to main content
Glama
crisphive

Crisphive

Official
by crisphive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Update a technician

updateTechnician
Idempotent

Update a technician's mutable details: contact info, address, job title, assignment tier, and day-start point. For day-start, set office to reuse business coordinates or home to provide address and coordinates.

Instructions

Update a technician

Updates mutable technician profile fields. start_location_type=office re-snapshots the current business address + coordinates (body address/start_location_lat/start_location_long ignored; requires business coordinates, else 400 BUSINESS_LOCATION_MISSING). start_location_type=home (or empty) uses the address + coordinates from the body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTechnician ID
emailNoEmail address. At least one of phone/email is required.
phoneNoPhone number in E.164 international format (`+16135550188`); a bare national number is rejected with PHONE_INVALID — see AddTechnicianReq.Phone. At least one of phone/email is required — enforced in the usecase; see the note on AddTechnicianReq.Phone for why no binding rule may decide it.
addressNoHome address (the day-start point when start_location_type=home).
full_nameYesThe person's full display name. Required; max 255 chars.
job_titleNoDisplay title.
join_dateNoFirst working day (YYYY-MM-DD).
assignment_tierNoCrew tier: lead / buddy / float (float = excluded from auto crew-assign).
business_group_idYesRole group. Discover IDs via GET /permission/groups.
start_location_latNoExplicit day-start latitude in decimal degrees (-90..90); when set it wins over the address geocode.
start_location_longNoExplicit day-start longitude in decimal degrees (-180..180); when set it wins over the address geocode.
start_location_typeNoDay-start point: home or office; explicit coordinates win when set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / phone / description
      Previous value: -"At least one of phone/email is required."New value: +"Phone number in E.164 international format (`+16135550188`); a bare\nnational number is rejected with PHONE_INVALID — see AddTechnicianReq.Phone.\nAt least one of phone/email is required — enforced in the usecase; see\nthe note on AddTechnicianReq.Phone for why no binding rule may decide it."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The description discloses non-obvious behavior beyond the annotations: when start_location_type=office, body address and coordinates are ignored and the business address is re-snapshotted, which may fail with BUSINESS_LOCATION_MISSING. This is valuable behavioral context that annotations alone do not provide.

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 compact and front-loaded with the purpose before diving into conditional behavior. The only minor issue is the redundant opening line repeating the title, but the rest of the description earns its place.

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 12-parameter update tool, the description covers the key non-obvious interaction that could cause incorrect calls. The rich schema covers parameter details, so the absence of return-value details is acceptable. It could be slightly stronger with an explicit statement about the typical response or required preconditions.

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 description coverage is complete, so the baseline is 3. The description adds meaningful interaction semantics between start_location_type and address/coordinate fields, clarifying which values are ignored and when an error can occur, which goes beyond the schema's individual field descriptions.

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 clearly states the tool updates mutable technician profile fields, which identifies the operation and resource. It does not explicitly name sibling alternatives but the verb and resource scope make the purpose distinguishable from create/delete/list tools.

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 description provides contextual parameter usage guidance, especially for start_location_type, but does not explicitly state when to use this tool versus alternatives like createTechnician or deleteTechnician. Usage is implied rather than directly stated.

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