Skip to main content
Glama

Open the dashboard in the browser

freeapply_open_dashboard
Read-onlyIdempotent

Opens the FreeApply dashboard in the browser so you can accept terms, adjust settings, answer pending questions, or review applications and replies; use it when action is required.

Instructions

Opens the local FreeApply dashboard in the user's browser, one tab (freeapply_get_status only reports its URL). Use: when the user must act there: accept the Terms, fill settings, answer questions waiting on them, review applications and replies. Not for reading data: other tools return it. Behavior: changes no data. Starts the dashboard if needed at http://127.0.0.1:7878 or the next free port; reachable only from this computer. Parameters: tab, the page to open: overview (default; shows the Terms until they're accepted), settings (setup fields), issues (Needs you: questions, sign-ups), applications or replies. Returns: {url, opened}. url null: it couldn't start (no free port); tell the user. opened false with a url: no browser launched; give the user the url.

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

Input Schema

NameRequiredDescriptionDefault
tabNoThe page to open (default overview).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.6
    • changedInput schema / properties / tab / description
      Previous value: -"Page: overview (default; shows the Terms until accepted), settings (setup fields), issues (Needs you: questions, sign-ups), applications, replies."New value: +"The page to open (default overview)."
  2. Changed1 schema field changedv1.0.4
    • changedInput schema / properties / tab / description
      Previous value: -"The page to open. Optional; default overview."New value: +"Page: overview (default; shows the Terms until accepted), settings (setup fields), issues (Needs you: questions, sign-ups), applications, replies."
  3. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / tab / description
      Previous value: -"Tab to show. Optional; default overview."New value: +"The page to open. Optional; default overview."
  4. Changed2 schema fields changedv1.0.1
    • addedInput schema / properties / tab / description
      Added value: +"Tab to show. Optional; default overview."
    • addedInput schema / properties / tab / enum
      Added value: +[
      +  "overview",
      +  "applications",
      +  "replies",
      +  "issues",
      +  "settings"
      +]
  5. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/non-open-world, but the description adds real context beyond them: no data is changed, the dashboard is started on demand with a port fallback (127.0.0.1:7878 or next free port), and it is reachable only from this machine. It also discloses the two failure modes and what the agent should do in each.

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?

Front-loaded with the action, then organized under Use:/Behavior:/Parameters:/Returns: labels so an agent can scan to the section it needs. Dense rather than padded — no sentence repeats a structured field verbatim, and the Returns guidance is load-bearing because there is no output schema.

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?

Though no output schema exists, the description documents the return shape ({url, opened}) and the meaning of each degenerate case, plus the localhost-only constraint and side effects. Nothing needed to invoke it correctly or interpret the result is missing for a single optional-enum-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100% with an enum, so the baseline is 3, but the description goes further by explaining what each enum value actually surfaces — overview (default; shows the Terms until accepted), settings, issues ("Needs you"), applications, replies. That is meaning the schema does not carry, and it matters for choosing a tab.

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 ("opens the local FreeApply dashboard in the user's browser") and immediately delimits it against the nearest sibling: freeapply_get_status only reports the URL while this one actually opens a tab. An agent can pick between the two without opening either 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?

Explicit when-to-use list ("when the user must act there: accept the Terms, fill settings, answer questions waiting on them, review applications and replies") paired with an explicit exclusion ("Not for reading data: other tools return it"). Both the selection condition and the anti-pattern are named.

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