Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Place open

place_open
Read-only

Opens one place of the app in full: what it is for, what the owner does there, its tabs or the sections of its page with what each holds, and the sections of each tab, each by its path. Analytics comes with what is counted and, for what is not, why and the owner's one step, and the business's own channel and code project with their numbers; Settings with each account's state and its profile as the platform shows it (name, bio and link, read now or within the day, with when; where a platform gives no bio or the read failed, it says so and why: then what the profile says is not known); Sell with every ad grouped by where it sends people (the business's website, each funnel's page, the other pages Marsell made, boosted posts, forms on ads), each group with what runs, what it spent and brought this month and what counts it. Open the place before describing it or naming where on it something is. One agent is agent_open, the cards waiting waiting_read.

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": {
      "place": "<place>"
    },
    "name": "place_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesthe place, by its name in lower case
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the operation as read-only and non-destructive, but the description adds substantive behavior: what 'in full' means for Analytics, Settings, and Sell, including time-sensitivity and failed profile reads. It does not cover auth, pagination, or broad error behavior, so it falls short of fully carrying the behavioral burden.

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 purpose is front-loaded, but the body is a dense semicolon chain enumerating return contents, which is harder to scan than necessary. Most clauses earn their place for a complex read tool, but the run-on structure reduces clarity.

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?

No output schema exists, so the description must carry return context; it does this for several places and includes useful caveats for profile reads. It is not complete for every enum place or for the project parameter, but it is substantially informative for a read operation.

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%, with the place enum and project parameter already documented in the schema. The description reinforces 'the place' but adds no meaning beyond the schema for the project id/name or its optionality.

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?

States a specific verb ('Opens') and resource ('one place of the app in full'), then enumerates the contents the agent will get. It also distinguishes agent_open and waiting_read for one agent and for cards, so it is not merely restating the title.

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

Usage Guidelines5/5

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

Tells the agent exactly when to use it: 'Open the place before describing it or naming where on it something is.' It also points to agent_open and waiting_read as sibling routes for one agent and for cards, leaving the routing condition clear.

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