Sprout Studio by Cotlet

Review inquiries and leads in Sprout Studio

sprout_studio_review_inquiries_and_leads

Read-onlyIdempotent

Review inquiries and leads in the user's own Sprout Studio account from ChatGPT, Claude or any AI agent. Returns how to do it in Sprout Studio step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Sprout Studio Cloud Browser. Sprout Studio's official API: Sprout Studio does not publish a general-purpose core API reference in the vendor sources checked on 12 November 2026.

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_review_inquiries_and_leads"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the surprising behavior that the tool returns instructions and performs no action itself, and by naming the browser tools that do the actual work. Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds the interaction model on top.

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 first two sentences are front-loaded and earn their place. The final sentence is an awkwardly structured fragment ('Sprout Studio's official API: ...') anchored to a specific date, which reads as boilerplate rather than actionable guidance.

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 parameterless guidance tool with no output schema, the description covers what is returned, that nothing is opened, and which tools continue the task. Only the absence of any note on what the returned steps look like or how large they may be keeps it from a 5.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly signals a parameterless call.

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 resource and scope (inquiries and leads in the user's own Sprout Studio account) and clarifies the tool's nature: it returns step-by-step instructions rather than performing the review. Sibling differentiation is implicit via the resource (activity log, shoot details) but never explicitly contrasted, keeping it below 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 Guidelines4/5

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

Explicitly frames the workflow: call this first to get screens/buttons/fields, then execute with the cotlet_browser_* tools. The 'opens nothing by itself' caveat prevents misuse. No explicit when-not-to-use case is stated, so it falls 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.

All Sprout Studio by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?