Skip to main content
Glama
Sign In
jotbus

jotbus

by Launchable-AI-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jotbus_help

Explains how the encrypted scratchpad works and guides connecting a workspace so coding agents can share notes and files.

Instructions

How Jotbus works and how to connect a workspace.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden, but the tool takes no parameters and performs no mutation, so the risk surface is small. It still does not say whether the call is read-only, whether it returns prose instructions or links, or whether it must be invoked before other Jotbus tools.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, though it reads as a title fragment rather than a full description. Nothing is wasted, but nothing is elaborated either.

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

Completeness3/5

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

For a zero-parameter help tool with no output schema, the description covers the topic broadly but leaves the return shape unspecified and never states the relationship to the workspace siblings. Adequate, but it should say more about when this beats calling list_workspaces or create_workspace directly.

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 has zero parameters and the schema is an empty object, so there is no parameter semantics for the description to explain. Baseline for a parameterless tool applies.

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?

The description names the resource (Jotbus help/documentation) and the two topics covered: how the product works and how to connect a workspace. That is enough to separate it from list_workspaces and create_workspace, which perform actions rather than explain them, though 'connect a workspace' is slightly ambiguous against the create_workspace sibling.

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: an agent can infer it should call this when it needs orientation on Jotbus or workspace connection. There is no explicit when-to-use trigger, no statement that it should be called before create_workspace, and no mention of alternatives.

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