Skip to main content
Glama

open_dinoctor

Launch the Dinoctor desktop app if closed and wait until its window is ready, returning open/ready status; call first and provide a download hint when installation is missing.

Instructions

Start the Dinoctor app on this computer if it isn't open, and wait (up to about 90 seconds) until its window is ready. Call this first. Returns { opened, ready }. Fails with a download hint if the app isn't installed. To only check whether it's open, use status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations it discloses blocking latency (~90s), the failure mode (download hint if not installed), and the return shape { opened, ready }. It doesn't say what happens when the app is already running (presumably opened=false) or whether it blocks other calls, so it stops short of full transparency.

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?

Four short sentences, front-loaded with the action, followed by timing, return value, failure mode, and the sibling pointer. Every sentence carries distinct information with no repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description supplies the missing return contract ({ opened, ready }), the wait bound, and the install-missing error behavior — everything needed to invoke and interpret the result correctly.

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 no parameters, so the baseline is 4; the description correctly spends no space on inputs and instead documents the returned flags, which the absent output schema leaves undocumented.

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?

"Start the Dinoctor app on this computer if it isn't open" names a concrete verb and resource, and adds scope (up to ~90s wait until the window is ready). It is clearly distinguishable from the read-only sibling 'status'.

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?

It states sequencing ("Call this first") and names the alternative for the non-mutating case ("To only check whether it's open, use status"), which is exactly the routing decision an agent needs.

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