Skip to main content
Glama
Sprout Studio MCP Server

Sprout Studio MCP Server

sprout_studio_click

Clicks a numbered element on the current Sprout Studio page using the element number from the last read, letting AI agents interact with page controls and workflow records.

Instructions

Click a numbered element on the current Sprout Studio page.

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": {
      "element": "<element>"
    },
    "name": "sprout_studio_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say what a click does to page state (navigation, form submission, re-render), whether element numbers become stale afterward, or what happens if the number is invalid.

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?

One short sentence, front-loaded with the action and resource, with no filler. It is efficient, though the terseness borders on under-specification rather than optimal density.

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?

Tool complexity is low (one required integer, no nested objects, no output schema to explain), so minimal prose is defensible. Still, for an unannotated state-mutating UI action, the absence of any note on post-click state or error behavior leaves a meaningful gap.

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 description coverage is 100% and the single 'element' parameter is documented as 'Element number from the last read.' The description adds no meaning beyond that, but with a fully documented, one-parameter schema the baseline of 3 applies.

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?

States a specific verb ('Click') and resource ('a numbered element on the current Sprout Studio page'), which distinguishes it from siblings like sprout_studio_read and sprout_studio_type. It stops short of naming an alternative explicitly, so it isn't quite a 5.

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 phrase 'numbered element from the last read' implicitly ties use to a preceding sprout_studio_read call, which is useful sequencing context. However, there is no explicit when-to-use vs. when-to-use-sprout_studio_type guidance and no stated prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.