Skip to main content
Glama

Update account

crm_update_account

Correct or deepen the account narrative. Only the fields you pass change. Provenance survives updates (CRM-9): why_them and source_url can be corrected, never blanked. Status moves have their own command, with its own rules.

PARKING IS NOT A STATUS MOVE (CRM-18). status is a judgement about where a pursuit sits; parking is a fact about what happened to it — both intake routes dead, the sponsor left, a reorganisation in flight. An account parked at researching is still at researching, and says why nobody is spending time on it. Parking needs a reason, is reversible with park="", and takes the account out of the worklists until it comes back. Effects: account narrative updated; account parked or unparked, with the reason kept.

Input Schema

NameRequiredDescriptionDefault
hookNoThe one-sentence opener you would actually use.
nameNoRename, if the company did.
parkNoWhy this account should be left alone, as a fact about what happened. Empty string unparks it. Read by whoever considers reopening it, so "both intake routes dead: form errors, research@ bounced 11 Sep" is useful and "not worth it" is not.
tierNo1–3. Tier semantics are yours; 1 usually means "worth a hand-written approach".
verticalNoIndustry vertical, your taxonomy.
why_themNoCorrecting, not blanking (CRM-9).
account_idYesThe account. An existing account id.
owner_noteNoWorking notes.
source_urlNoCorrecting, not blanking (CRM-9).
trigger_eventNoWhat changed that makes now the moment. A fact, with the source in source_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description provides critical behavioral guarantees beyond the structured fields, such as 'Only the fields you pass change' and 'Provenance survives updates (CRM-9).' It also details the functional logic of the 'park' state (reversible with park='', moves account out of worklists), which is crucial behavioral context for an updater tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is highly discursive and dense. It sacrifices conciseness in favor of comprehensive detail and business context. While the structure is logical (goal -> constraints -> behavioral rules), the sheer volume of explanatory text makes it less immediately readable than a perfectly concise definition.

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

Completeness5/5

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

Given the tool's complexity—involving nuanced operational states (parking), historical constraints (provenance), and the difference between status and fact—the description is remarkably complete. It covers the most important edge cases and behavioral constraints an agent needs before making a call.

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

Parameters5/5

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

While the schema coverage is 100% (setting a baseline), the description adds essential operational semantics that the schema lacks. Examples include explaining that 'park' is a 'fact about what happened,' why `why_them` cannot be blanked, and that '1' in `tier` means 'worth a hand-written approach.' This adds significant decision-making value to parameter interpretation.

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 purpose is clearly defined as correcting or deepening the account narrative. However, while it is clear what the tool does, the description relies heavily on specialized CRM terminology, which could be slightly clearer in distinguishing itself from a general 'customer' update tool, though its focus on 'account' provides a good distinction.

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?

This definition provides excellent usage guidelines by setting strict boundaries: distinguishing between 'status moves' and 'parking,' and explaining the unique semantics of the 'park' field. It directly addresses common operational pitfalls for this type of tool, significantly aiding agent selection.

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.