Skip to main content
Glama
Sign In
Workato Dev MCP

Workato Dev MCP

by gmunro-lyft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

upsert_properties

Create or update account properties in Workato using a JSON object string of name-value pairs.

Instructions

Create/update account properties. properties_json is a JSON object string {name: value}.

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": {
      "properties_json": "<properties_json>"
    },
    "name": "upsert_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
properties_jsonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only states the operation and property format, but does not disclose whether properties are merged or replaced, whether the operation is idempotent, or any side effects or permissions required.

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?

The description is compact—two sentences, no filler—and both sentences contribute useful information: the tool's purpose and the input format. It is appropriately sized.

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?

Given the tool's simplicity (1 param, no output schema, no annotations), the description covers the basic purpose and parameter format. However, it omits behavioral details like upsert semantics (merge vs. replace) and any side effects, which creates slight invocation ambiguity but is acceptable for a minimal tool.

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?

The schema merely defines properties_json as a string with no description. The description adds context by specifying it is a JSON object string in the format {name: value}, but stops short of providing examples or clarifying the exact structure of name/value pairs, leaving some ambiguity.

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 clearly states the tool's function with 'Create/update account properties', using a specific verb and resource. It also differentiates itself from the sibling read tool 'get_properties' by indicating a mutation operation.

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

Usage Guidelines2/5

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

No guidance is provided regarding when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or context for when an upsert should be preferred over other property-related operations.

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