Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

See the business setup

get_setup
Read-only

The setup the owner opened with Connect your AI, as an owner reads a business: what is filled (the business, who it's for, what it sells with every product's name, price and number of pictures, how it looks and sounds, where it is, who it's up against, guides, answers), its own characters with their looks and its own places, the read's questions still open, the preferences questions to ask the owner (with who Marsell talks to for them, in preferences.reach), the files on the project, and what could still be added with which tool. Start here, fill it from what you know of the business (its site, its code and docs, its files, what the owner told you), then finish_setup.

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": "get_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral context by detailing what the setup contains and how it fits into the workflow before finish_setup, though it does not describe return format or parsing details.

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 content is relevant, but it is delivered as one long, tangled sentence with a nested parenthetical list, making it harder to scan than it should be. It is appropriately complete for a complex setup read, but the structure is weak.

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?

With no parameters and no output schema, the description carries most of the burden of explaining what the tool returns. It does this by enumerating the setup's major content areas and workflow, though it does not specify the exact response shape or field names beyond preferences.reach.

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?

This tool takes zero parameters, so the baseline is 4. The description adds no parameter semantics because there are none to explain.

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 makes clear that this is a read of the business setup and enumerates the setup's contents, including filled sections, characters, places, open questions, files, and recommended additions. It does not explicitly differentiate itself from close siblings such as get_overview or business_context_read, so it falls short of 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?

The description gives clear usage guidance: start here, fill the setup from known business context, then call finish_setup. It does not state when not to use this tool or name alternative setup-reading siblings, so it is not a full 5.

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

All Marsell toolsInspect
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