Skip to main content
Glama
Sign In
Workato Dev MCP

Workato Dev MCP

by gmunro-lyft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_properties

Fetch account properties and feature flags matching a name prefix, enabling quick retrieval of configuration settings.

Instructions

Get account properties whose names start with a prefix (config/feature flags).

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": {
      "prefix": "<prefix>"
    },
    "name": "get_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Get' implies a read-only operation, and the prefix filter is clarified. However, the description does not state what the response contains (names, values, or both), nor any permissions or rate limits. For a read tool, this is a moderate transparency gap.

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?

A single, clear sentence that immediately states the verb, object, and filter. No extraneous information.

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 simple one-parameter read tool, the description covers the core input and purpose. However, the absence of an output schema or any description of the return format leaves some ambiguity about what the agent can expect, and there is no mention of pagination or result limits.

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?

The description explicitly explains that the 'prefix' parameter filters property names by their starting characters, adding critical meaning to an otherwise bare schema. It also hints at the naming convention (config/feature flags), which helps the agent construct valid prefixes.

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 retrieves account properties filtered by a name prefix. The parenthetical '(config/feature flags)' provides additional context on the property types, making the purpose unambiguous and distinct from write operations like upsert_properties.

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 implies the tool is for reading properties with a given prefix but does not explicitly mention when to use it over alternatives, nor does it discuss limitations or exclusions. There is no comparison with sibling tools like upsert_properties, so usage guidance is only implied.

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