Skip to main content
Glama
Sprout Studio MCP Server

Sprout Studio MCP Server

sprout_studio_guide

Get step-by-step guidance for Sprout Studio sign-in and screens, plus workflows for photography inquiries, shoots, client paperwork, invoices, and galleries.

Instructions

How to work in Sprout Studio (photography inquiries, shoots, client paperwork, invoices and galleries): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sprout_studio_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Sprout Studio, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It makes clear the tool returns guidance content (screens, sign-in link) rather than performing a mutation, which is useful behavioral framing, but it says nothing about the shape or size of the returned guidance or whether the response is static or tailored to the task.

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?

Two tight sentences with no filler; the scope of the app and the covered workflows are front-loaded, and the imperative 'Call this first' closes it. It could be slightly tighter given the parenthetical list, but nothing is wasteful.

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-optional-parameter orientation tool with no output schema, the description conveys enough: what domain it covers, what content it exposes, and that it precedes other calls. The only residual gap is what the returned guidance looks like, which is modest given the tool's simplicity.

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 coverage is 100% and the single parameter is well documented in-schema as free-text 'in your words'. The description never mentions the task parameter, so it adds no meaning beyond the schema and leaves unclear how a free-form task shapes a supposedly static guide. Baseline 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?

The description names the resource (Sprout Studio) and enumerates what the guide covers — screens, inquiry/shoot/paperwork/invoice/gallery workflows, and the sign-in link — so an agent knows this is orientation documentation rather than an action. It implicitly distinguishes itself from the action-oriented siblings (click, open, type, read, status, close) by framing itself as 'how to work in' the app.

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

Usage Guidelines4/5

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

'Call this first' is an explicit, actionable ordering directive that tells the agent when to reach for this tool relative to everything else. It does not state when-not-to-use or name a specific sibling as an alternative, which keeps it short of a 5.

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