Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Agent open

agent_open
Read-only

Opens one agent, by its id, with everything about it in one call: what it does, its rhythm, what its switch does and where it stands, its cards waiting, and from its own records its last run in full, everything it found (the Creator agent: every creator by name with who fits; the SEO agent: each buyer question and how each assistant answered; the Reddit agent: each of its checks), what waits for the owner, and what it needs before it can run. An agent with nothing behind it says so; an id that does not work on this business is refused with the ids that do.

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": {
      "id": "<id>"
    },
    "name": "agent_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe agent's id, as agents_read and input.app.agents give it
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

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/destructive annotations, it discloses real behavior: empty agents are reported as such, and an id outside the business is refused with the valid ids returned. Return-contents disclosure is extensive. It stops short of permissions, rate limits, or how large the 'last run in full' payload can get.

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 lead clause is well front-loaded, but the second half is a single sprawling sentence with stacked clauses and parenthetical per-agent examples ('what it does, its rhythm, what its switch does and where it stands…'). Informative, yet several phrases are vague filler that could be tightened.

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 what comes back, and it does so thoroughly, including empty-state and invalid-id behavior. Only minor gaps remain (payload size, whether the response is cached) for a two-parameter 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%, so both params are already documented; the description only reinforces the id-based lookup and hints at business scoping via 'an id that does not work on this business.' It adds no format or fallback detail beyond the schema, matching the baseline for full coverage.

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 verb and resource — opening one agent by id — and enumerates the payload (definition, rhythm, switch state, cards, last run, agent-specific findings). An agent can tell this is the single-agent detail view, but the description never names a sibling (agents_read, card_read, waiting_read) to sharpen the contrast.

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

Usage Guidelines3/5

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

Usage is only implied: 'in one call' hints you should prefer this over several narrower reads, but there is no explicit when-to-use, when-not, or named alternative such as agents_read for listing. The routing to agents_read/id discovery lives only in the schema description, not the tool description.

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