Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Offerings read

offerings_read
Read-only

Reads what the business offers, as the app shows it: whatYouOffer (Brand's What you offer: the products, services and initiatives the read of its pages found), sell (Sell's ways in: its plans, services and products with their prices), and removed (what the owner took off). The same offering can be named differently in each list. Read it before offering_remove or offering_restore; the products' own pictures and details are on Brand (place_open brand).

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

Input Schema

NameRequiredDescriptionDefault
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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral context: removed items are included in the result and the same offering may appear under different names per list, which warns the agent against naive name-based joins.

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?

The purpose and the three list names are front-loaded, and the second sentence carries the operational advice. The parenthetical glosses ('Brand's What you offer: the products, services and initiatives the read of its pages found') are wordy but do disambiguate jargon.

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 output schema, the description carries the burden of describing returns, and it does so by naming the three top-level lists and their meaning. It omits any note on result size or pagination and on default project scoping, which are the only remaining gaps for a single-optional-param read tool.

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 'project' parameter is documented in the schema as optional when the account has one project. The description adds nothing about the parameter, but with full schema coverage and only one optional param, the baseline 3 applies.

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 and resource ('Reads what the business offers') and then enumerates the exact contents returned: whatYouOffer, sell, and removed. It also disambiguates from siblings by naming offering_remove/offering_restore and pointing to Brand/place_open for product-level detail, so an agent can distinguish it without opening a schema.

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 instructs 'Read it before offering_remove or offering_restore', giving a concrete call ordering, and redirects to place_open brand for pictures and details. It lacks an explicit when-not or a named alternative for the general listings case, but the sequencing guidance is 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