Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Situation read

situation_read
Read-only

The rest of the business's situation, behind the brief in input.situation: pass one name from input.situation.more and get that part whole (the funnel's arithmetic, the calendar's work and later slots, a number day by day and by channel, why a number is not counted and the owner's step, the work that failed or was cancelled and why, the site's checks, the catalogue's changes, what may be claimed). Pass all only when the question needs most of it: it is large. Returns { part, value }; a name it does not have is refused with the list of names. A part inside a part may be named by its path, with dots.

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": {
      "part": "<part>"
    },
    "name": "situation_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYesA name from input.situation.more, or all for everything.
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/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavior beyond that: return shape { part, value }, refusal with the list of names for unknown parts, and dot-path access to nested parts.

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 is front-loaded, and each sentence carries useful information about selection, size tradeoff, return shape, refusal, and nesting. The long parenthetical list and dense run-on first sentence make it less readable than ideal.

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 two-parameter read tool with annotations and no output schema, it covers invocation, return shape, invalid input handling, and nested paths. The main remaining gap is that it assumes familiarity with input.situation and input.situation.more.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that part names come from input.situation.more, that all is valid, and that nested parts may be named by dot paths; project semantics are left to the schema.

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 read operation: fetch one named part of the business situation behind input.situation, with examples of what those parts include. It does not explicitly distinguish itself from sibling reads such as business_context_read, so it stops 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?

Tells the caller to pass one name from input.situation.more and to pass all only when the question needs most of it because it is large. It gives clear one-vs-all guidance, but does not name alternative sibling tools for comparison.

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