Skip to main content
Glama
Sign In
ochi

ochi

by jennywassweet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_status

Check whether the ochi Chrome session is running without starting it, so you can confirm web page reading is available before use.

Instructions

Is the ochi Chrome running? (does not start it)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it usefully discloses the key side-effect boundary: this is a passive check that will not launch Chrome. It says nothing about cost, blocking behavior, or what a negative result means, but for a zero-arg status probe with an output schema those gaps are small.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two fragments, the core question front-loaded, and the disambiguating caveat immediately after it. Nothing is wasted and nothing is buried.

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?

Return values are covered by the existing output schema and the tool is trivially simple, so the description is nearly complete. It could add one clause on when to reach for this versus browser_start, but nothing required to call it correctly is missing.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The absence of arguments is consistent with a pure status probe.

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?

The description gives a specific check ('Is the ochi Chrome running?') against a named resource, and the parenthetical 'does not start it' directly separates it from the sibling browser_start. An agent can pick this tool without opening any 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?

The exclusion 'does not start it' effectively routes the agent to browser_start when launching is needed, so the when-not case is explicit. However, browser_start is not named directly and no other usage context (e.g., call before fetch/snapshot) is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools