Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Journal read

journal_read
Read-only

Reads the journal of Marsell's own planning passes (the weekly plan and the daily passes), newest first: each run's kind (weekly or daily), what started it, when, whether it finished well, its summary, what it was waiting for, its notes, the plan revision it wrote and its cost in tokens. Use it to say what the passes decided and why; what was done in the app is timeline_query, the plan's work itself work_list. Chat turns are not runs here.

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": {
      "n": "<n>"
    },
    "name": "journal_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYesHow many of the latest runs, 1 or more; null for every finished run since the last weekly pass, ending with that pass.
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.3/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 safety is covered. The description adds real context beyond that: results are newest-first, and the scope boundary that chat turns are excluded. It stops short of discussing volume limits or how large a run record can be, so not a 5.

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?

Front-loaded with the verb and resource, then the field inventory, then the routing guidance — a sensible order. The field list is long but earns its place since there is no output schema; the only slight drag is that it reads as one dense run-on sentence.

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 usefully enumerates what each run record contains, and it names the sibling tools that cover adjacent data. It is nearly complete; minor gaps are how 'Marsell' relates to the caller and whether results are bounded by anything other than 'n'.

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 description coverage is 100%, and the schema already explains both 'n' (count, or null for all runs since the last weekly pass) and 'project' (id or exact name, optional with a single project). The description adds no syntax or format detail beyond that, so the baseline of 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 the journal of Marsell's own planning passes') and enumerates the record fields (kind, trigger, timing, outcome, summary, waiting, notes, revision, token cost). It explicitly distinguishes itself from timeline_query and work_list, so an agent can route correctly without opening another schema.

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?

Gives explicit positive usage ('to say what the passes decided and why') and negative routing ('what was done in the app is timeline_query, the plan's work itself work_list'). It also carves out a scope exclusion ('Chat turns are not runs here'), leaving nothing to inference.

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