Skip to main content
Glama
Sign In
Timbre

Timbre

by alejandrosml
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

connect_app

Idempotent

Connect Timbre to a supported Mac assistant so it can use Timbre for mail automatically through a skill or rule; the change is reversible.

Instructions

Connect Timbre to another assistant on this Mac: chatgpt (the ChatGPT desktop app, Work and Codex), gemini (Google's Antigravity), mistral (Mistral Vibe in the terminal), lm_studio (models run on the Mac: DeepSeek, Mistral, Qwen…), raycast (Raycast AI: DeepSeek, Grok, Mistral, GPT…), perplexity (its Mac app), claude (Claude's desktop app, for a Timbre installed apart) or gemini_cli. A settings file changes once the user clicks in a window, with a skill or rule so the assistant uses Timbre for mail unasked; undo takes it back. Raycast and Perplexity: their own settings open. The same Timbre and permissions.

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": {
      "app": "<app>"
    },
    "name": "connect_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes"chatgpt" (the ChatGPT desktop app, Work and Codex), "gemini" (Google's Antigravity, desktop app and command line), "mistral" (Mistral Vibe in the terminal), "lm_studio" (models run on the Mac: DeepSeek, Mistral, Qwen…), "raycast" (Raycast AI: DeepSeek, Mistral, Grok, GPT, Gemini…), "perplexity" (its Mac app), "claude" (Claude's desktop app, when Timbre was installed apart from it) or "gemini_cli".

Output Schema

NameRequiredDescriptionDefault
fileYesThe settings file changed; empty when the app keeps its settings itself.
noteYes
statusYesconnected, already, opened (the other app's own window takes it from there), awaiting_approval or cancelled.
undo_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations show an idempotent, non-destructive mutation; the description adds that a settings file changes only after the user clicks in a window, that a skill or rule is installed so the assistant uses Timbre for mail unasked, and that undo reverses it. The permission mechanism remains vague.

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 purpose is front-loaded, but the long app enumeration duplicates the schema and the fragmented clauses make it denser than necessary.

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?

For a one-parameter setup tool with an output schema and annotations, the description covers the target apps, side effects, and undo behavior. Permission details are still thin, but nothing critical for invocation is missing.

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 input schema already fully enumerates all valid app values. The description largely repeats that enumeration rather than adding selection or formatting guidance beyond the schema.

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 ('Connect') and resource ('Timbre to another assistant on this Mac'), and enumerates supported app targets. This makes it clearly distinct from the mail-operation sibling tools.

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?

Implies use when the user wants to hook Timbre into a desktop or terminal assistant and notes that Raycast and Perplexity open their own settings. However, it gives no explicit when-not guidance or prerequisites beyond the vague 'same Timbre and permissions'.

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